Booting the Blaze
Michael Payne
I'm trying to get Android up and running on the Blaze.
I've used pre-built binaries for L27.INC1.8.2 OMAP4 Froyo ES2.
Everything on the SD card I'm using looks fine. The partitions look
great, file system is fine. The graphics package installed without a
hitch. However when I try and boot it, I listen on the appropriate
usb port through hyperterminal and/or minicom and only get gibberish.
I checked my jumper settings, and I am operating in Flashing/Terminal
mode (S6 [1:4] 0111).
I have the S2 jumpers set at S2 [1:8] 10100000 for a default boot
order of USB/MMC (or so this slip of paper that shipped with it
claims).
I've played with the serial settings in both minicom and
hyperterminal, and the closest I get is a line of gibberish. This
falls in line with about what I'd expect (1 line of text, prompting
for boot args). Sending something to the Blaze does nothing
(absolutely no response from the device). This was obtained at 115200
8N1 with no hardware/software controls.
Everything in the documentation I see claims this is all correct. Am
I missing something? There's not a lot of info out there right now,
and I'd love to know if there's a better place to find it.
Thondar, Geetha
Note that UART Configuration DIPSW is indicated incorrectly as S6 in the Blaze Quick Start Guide. This is S3 as printed on the main board. Please try this out.
Michael Payne
actually S3. It doesn't change how my jumpers are set though. Same
post as above, except substitute S3 for S6.
- Mike
James Athey
1. Set the Heads to 255 and Sectors to 63 when partitioning the SD card. http://omappedia.org/wiki/Android_SD_Configuration#Configure_SD_Card I didn't follow this step the first time, because it seemed silly. It actually does matter.
2. Make sure S2 has switches 2 and 5 on and everything else off. http://omappedia.org/wiki/Android_Prebuilt_Platform_Configuration#Blaze_sEVM4430
3. Use the correct MLO for your board. My new blaze is a GP board, so I copied gp_MLO to the fat32 filesystem and renamed it to just MLO.
4. Copy uImage_L27.8.2_CCD to the fat32 filesystem and rename it to just uImage.
5. This doesn't apply to your current problem, but it's much saner to set the UID and GID to 1000 for all files on the ext3 filesystem; don't set the permissions to 777 as suggested by omappedia. Extract the tarball directly to the freshly formatted filesystem with the --preserve-permissions flag. After installing the graphics package, Ducati binaries, and wireless firmware, use "chown -R 1000:1000 <SD ext3 mountpoint>" to set the correct ownership.
6. The wireless firmware installer does not put the firmware in the right location. Move it to system/etc/wifi (if I recall correctly.)
-James
-----Original Message-----
From: omapd...@googlegroups.com [mailto:omapd...@googlegroups.com] On Behalf Of Michael Payne
Sent: Friday, March 04, 2011 5:56 PM
To: omapdiscuss
Subject: Booting the Blaze
Michael Payne
Thanks again guys.
- Mike
mbarton888
A few weeks ago I could not get the Blaze to boot with the pre-built
stuff, so did my own build: build the L27.7.2 community-supported
version. I realize this is older than what you are trying to use. Used
the latest u-boot instead of what omappedia recommends, and got it all
running. I suspect the pre-built is good for some specific version of
hardware or software components, but may not run on specific versions
of boards or combinations of software. Anyway, if you were to get it
running on any version, you then know all your switch settings are
good.
Matthew Barton
Neusoft America
On Mar 5, 12:12 pm, Michael Payne <michael.joseph.pa...@gmail.com>
wrote:
> off (factory setting), I figured there could only be 64 (2^6) jumper
> combos. So I basically just started cycling through them. Got the same
> jumper combo that you mentioned here by trial and error. I didn't actually
> finish booting it because the lab closed down, but I'll try this on Monday.
>
> Thanks again guys.
>
> - Mike
>
>
>
>
> > I just went through the same mess, seeing only gibberish, when I first
> > tried to get my new Blaze to boot. Make sure you've done the following:
>
> > 1. Set the Heads to 255 and Sectors to 63 when partitioning the SD card.
> >http://omappedia.org/wiki/Android_SD_Configuration#Configure_SD_CardI
> > didn't follow this step the first time, because it seemed silly. It
> > actually does matter.
> > 2. Make sure S2 has switches 2 and 5 on and everything else off.
>
> - Show quoted text -
Michael Payne
so I'll try building it as mentioned above. The MeeGo image came
right up though, so I know I'm on track.
Thanks again for the help so far guys.
- Mike
Michael Payne
so I'll try building it as mentioned above. The MeeGo image came
right up though, so I know I'm on track.
Thanks again for the help so far guys.
- Mike
On Mar 6, 3:12 am, mbarton888 <matthew.bar...@ieee.org> wrote:
Michael Payne
so I'll try building it as mentioned above. The MeeGo image came
right up though, so I know I'm on track.
Thanks again for the help so far guys.
- Mike
On Mar 6, 3:12 am, mbarton888 <matthew.bar...@ieee.org> wrote:
James Athey
Having gotten the L27.8.2 release to boot, I set out to get L27.INC1.11.1 working, since that uses Gingerbread instead of Froyo. Following the directions posted at http://www.omappedia.org/wiki/L27.INC1.11.1_OMAP4_GingerBread_ES2_Release_Notes, I checked out and built all of the sources, and installed them to an 8 GB SD card. When I only got garbage on the serial console from that, I tried repartioning that card as a 4 GB card, to no avail.
On the other hand, if I copy the uImage, MLO, and u-boot.bin that I built myself to the old 4 GB card that does work, at least the bootloader starts up!
Jayabharath, Goluguri
Does anyone know if the Blaze supports booting from SD cards larger than 4 GB?
Haven't tried this on a Blaze. But certainly Pandaboard's booth file with 8GB SD cards - I dont see a reason why Blaze should be any different..
--Jay
Michael Payne
- Mike
James Athey
I just noticed the following line on http://omappedia.org/wiki/Booting_Android:
“Note: If the device does not boot up with your SDHC card, try partitioning the same SDHC card again. If still the device does not boot up try another SDHC card. Many times changing the SDHC card solves the boot up problems.”
I suppose it’s a small comfort to know that at least one other person has seen the same problem. It would be nice to know WHY a particular card won’t boot…
James Athey
Software Engineer
-------------------------
2350 Corporate Park Dr. / Suite 510 /
Herndon, VA 20171
203-675-8726 (mobile)
This e-mail and all attachments are intended solely for use by the intended recipient and may contain confidential / proprietary information of BTS, LLC or export controlled technical data, subject to important disclaimers and conditions including restrictions on the use, disclosure, transfer or export (to non-US persons) of such information and technical data available at http://www.unleashbts.com/legalnotices/
From: omapd...@googlegroups.com [mailto:omapd...@googlegroups.com]
On Behalf Of Michael Payne
Sent: Tuesday, March 08, 2011 4:51 PM
To: omapd...@googlegroups.com
Subject: Re: Booting the Blaze
I booted MeeGo on the Blaze with a 16 GB, so I don't see why not.
- Mike
Jayabharath, Goluguri
I just noticed the following line on http://omappedia.org/wiki/Booting_Android:
“Note: If the device does not boot up with your SDHC card, try partitioning the same SDHC card again. If still the device does not boot up try another SDHC card. Many times changing the SDHC card solves the boot up problems.”
Most people tend to partition/format incorrectly. Certain times the SDcard would be corrputed during the process which could potentially make it un usable - switching to a new SD card helps. This was the intent behind the above statements.
--jay
buster
then adjust those numbers in x-loader and u-boot.
- Alan
On Mar 8, 11:05 am, James Athey <james.at...@unleashbts.com> wrote:
> Does anyone know if the Blaze supports booting from SD cards larger than 4 GB?
>
> On the other hand, if I copy the uImage, MLO, and u-boot.bin that I built myself to the old 4 GB card that does work, at least the bootloader starts up!
>
normanc
S2 switch is 2 and 5 on, rest are off
S3 switch is 1 is off, rest are on.
I power up, and the Blazer is giving out the garbage data to the
mini-console port ( the 3rd ports out from 4 )
serial port is config as 115200, 8n1n,
and ideal,
thanks
nroman
" “ tØ b U
lDyªi.H¯a£‘¡;”OUØW¶ù¥!«äèï
\ÒnçP÷DiµëÖ†®&’OMï.Dm¬™Uÿ# tØ b U
lD
yªi.H¯a£‘¡;”OUØW¶ù¥!«äèï\ÒnçP÷DiµëÖ†®&’OMï.Dm¬™Uÿ# tØ b U
lDyªi.H¯a
£‘¡;”OUØW
¶ù¥!«äèï\ÒnçP÷DiµëÖ†®&’OMï.Dm¬™Uÿ# tØ b U
lDyªi.H¯a£‘¡;”OUØW¶ù
¥!«äèï\ÒnçP÷Di
µëÖ†®&’OMï.Dm¬™Uÿ# tØ b U
lDyªi.H¯a£‘¡;”OUØW¶ù¥!«äèï
\ÒnçP÷DiµëÖ†®&’OMï.Dm¬™U
ÿ# tØ b U
lDyªi.H¯a£‘¡;”OUØW¶ù¥!«äèï
\ÒnçP÷DiµëÖ†®&’OMï.Dm¬™Uÿ# tØ b U
lD
yªi.H¯a£‘¡;”OUØW¶ù¥!«äèï\ÒnçP÷DiµëÖ†®&’OMï.Dm¬™Uÿ# tØ b U
lDyªi.H¯a
£‘¡;”OUØW
¶ù¥!«äèï\ÒnçP÷DiµëÖ†®&’OMï.Dm¬™Uÿ# tØ b U
lDyªi.H¯a£‘¡;”OUØW¶ù
¥!«äèï\ÒnçP÷”
normanc
in the SD card.
this issue is even i unplug the SD card from the board and power up
the Blaze, it still give me this
garbage data.
thanks
norman
pramod
Hi,Did you find solution for this?
I am facing the same problem,Unable to Boot Blaze 4430 first time with SD
card.Getting Garbage data at Minicom.
Mayank Mangla
--
You received this message because you are subscribed to the Google Groups "omapdiscuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to omapdiscuss...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.