Hello
I bought BB on the ebay and it's appeared to be RevA. I tried to
connect dispaly via DVI but it was no signal on display. When i try to
connect via RS232 (with SD-card and boot files from
http://code.google.com/p/beagleboard/wiki/BeagleboardRevCValidation)
there is 40T in the console and nothing. There is nothing in the
console without SD card. I tried to connect headphones to it but no
sound.
How can i make sure it's working and run linux?
Plz help me.
Well, we only built a very few Rev A boards and it was never actually produced in production. I can’t even remember that far back. I doubt anyone that had a Rev A is even still using it so you won’t find very many people out there that would have a board like yours. I am disappointed that someone would actually put up a rev A for sell as old as that board was and the fact it was never actually produced…
40T means there is no SW loaded into the NAND or on the SD card. You might try going to the validattion website http://code.google.com/p/beagleboard/wiki/BeagleboardRevCValidation and follow the instructions there. I think for the most part it should work, but there will be some differences. The Rev A did have issues and that is why we never produced it.
The best I can offer is to say give it a try.
Gerald
Thanks for reply. I have ASSY REV A3 on the one side of the board and
SERIAL#CC0-010377 500-5000-001 REV A on the other side. Although I
have the correct DC power jack pinout.
I already tried that link but still 40T and nothing. Also if I try to
power it not from USB but from 5VDC it writes 40T without any delay
with and without SD-card.
I also tried to boot it from RS232 using this util
http://code.google.com/p/omap-u-boot-utils/
Pserial works ok, but ukermit hangs. Here is the log:
D:\AccessPort\x32>pserial.exe -p com8 -f x-load_revc_v3.bin.ift
Waiting For Device ASIC ID: Press Ctrl+C to stop
ASIC ID Detected.
Sending 2ndFile:
Downloading file: 100.000% completed(20392/20392 bytes)
File download completed.
D:\AccessPort\x32>ukermit.exe -p com8 -f u-boot-f_revc_v3.bin
Failed after 4 retries in sequence 0 - success send = 0 bytes
Data transmit failed
What else can I try?
Yury
I am not familiar with the log you have sent. It is not what I am used to seeing. Are you attempting to do a serial boot process?
If you format the SD card correctly and copy the files correctly you should be able to reflash the NAND. I would try this agian and hold down the user butter while powering up the board. Once it finds the SD card, it should refalsh the NAND. From there you should come up in UBoot.
Gerald
Yes i tried to boot from serial.
I also tried today with another sd-card but all the same although i
follow the instruction exactly
Well, I am not exactly sure how to help you. As I said, this is an old board with an old processor and several issues.
If you are willing, you can request an RMA and we will see if there is anything we can do with it.
Gerald
it's seems i finally get it working! I used Flashboot util for
formating SD-card instead of recommended HP util.
Do you think i have RevA or RevB BB? Here is what i got:
Texas Instruments X-Loader 1.4.2 (Feb 19 2009 - 12:01:24)
Reading boot sector
Loading u-boot.bin from mmc
U-Boot 2009.01-dirty (Feb 19 2009 - 12:23:21)
I2C: ready
OMAP3530-GP rev 2, CPU-OPP2 L3-165MHz
OMAP3 Beagle board + LPDDR/NAND
DRAM: 128 MB
NAND: 256 MiB
Using default environment
MUSB: using high speed
In: serial usbtty
Out: serial usbtty
Err: serial usbtty
Board revision Ax/Bx
Glad you got it working! one note on the HP utility. I have seen instances where FAT32 does not always work. I generally just use FAT for the formatting.
It looks like from the printout it is indeed a Rev A board.
Gerald
As I am on Linux (Fedora 12), will mkdosfs format the card properly?
Thanks
Bob
Yes it does, with "-F 32" or with synonyms mkfs.vfat, verification at
any time with fsck.vfat. I used it to build my 2 16G cards.
Regards
Sid.
It's me again. I still can't run linux. It hangs on booting the
kernel. Here is the log
40aT.........................................
Texas Instruments X-Loader 1.4.2 (Feb 19 2009 - 12:01:24)
Reading boot sector
Loading u-boot.bin from mmc
U-Boot 2009.01-dirty (Feb 19 2009 - 12:23:21)
I2C: ready
OMAP3530-GP rev 2, CPU-OPP2 L3-165MHz
OMAP3 Beagle board + LPDDR/NAND
DRAM: 128 MB
NAND: 256 MiB
Using default environment
MUSB: using high speed
In: serial usbtty
Out: serial usbtty
Err: serial usbtty
Board revision Ax/Bx
Serial #00000000000000000000000000000000
Hit any key to stop autoboot: 10 9 8 7 6 5 4
3 2 1 0
reading boot.scr
679 bytes read
Running bootscript from mmc ...
## Executing script at 80200000
reading x-load.bin.ift
20392 bytes read
***** Replacing x-load *****
Usage:
nand - NAND sub-system
HW ECC selected
NAND erase: device 0 offset 0x0, size 0x80000
Erasing at 0x0 -- 25% complete.
Erasing at 0x20000 -- 50% complete.
Erasing at 0x40000 -- 75% complete.
Erasing at 0x60000 -- 100% complete.
OK
NAND write: device 0 offset 0x0, size 0x20000
131072 bytes written: OK
NAND write: device 0 offset 0x20000, size 0x20000
131072 bytes written: OK
NAND write: device 0 offset 0x40000, size 0x20000
131072 bytes written: OK
NAND write: device 0 offset 0x60000, size 0x20000
131072 bytes written: OK
reading u-boot-f.bin
275928 bytes read
***** Replacing u-boot *****
Usage:
nand - NAND sub-system
SW ECC selected
NAND erase: device 0 offset 0x80000, size 0x160000
Erasing at 0x80000 -- 9% complete.
Erasing at 0xa0000 -- 18% complete.
Erasing at 0xc0000 -- 27% complete.
Erasing at 0xe0000 -- 36% complete.
Erasing at 0x100000 -- 45% complete.
Erasing at 0x120000 -- 54% complete.
Erasing at 0x140000 -- 63% complete.
Erasing at 0x160000 -- 72% complete.
Erasing at 0x180000 -- 81% complete.
Erasing at 0x1a0000 -- 90% complete.
Erasing at 0x1c0000 -- 100% complete.
OK
NAND write: device 0 offset 0x80000, size 0x160000
1441792 bytes written: OK
***** Erasing environment settings *****
Usage:
nand - NAND sub-system
NAND erase: device 0 offset 0x160000, size 0x20000
Erasing at 0x160000 -- 100% complete.
OK
reading normal.scr
603 bytes read
***** Executing normal.scr *****
## Executing script at 80200000
reading uImage.bin
2578044 bytes read
***** Kernel: /dev/mmcblk0p1/uImage.bin *****
reading ramdisk.gz
7999649 bytes read
***** RootFS: /dev/mmcblk0p1/ramdisk.gz *****
## Booting kernel from Legacy Image at 80200000 ...
Image Name: Linux-2.6.28-omap1
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2577980 Bytes = 2.5 MB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing
Linux.....................................................................................................................................................................
done, booting the kernel.