|
BeagleboardRevCValidation
Beagle Board Diagnostic Tools and Procedure
Validating Beagle Board (Rev C and Rev B) with Tests / DiagnosticsSetupPrepare MMC/SD card for Validation
http://selfdestruct.net/misc/usbboot/SP27213.exe Copy the following files on to MMC in the following order:
NOTE: If you don't want to flash the bootloader on NAND then copy Regular script file as boot.scr Sources for board testing can be found at
Board Setup for Validating
Beagle validationPress the "User" switch/button on the Beagle Board. While it’s still pressed, give power to (turn ON) the Beagle Board, by inserting the USB A connector side of the USB cable to HOST machine, then release the switch. This should bring up u-boot and the following Board Diagnostic tests will be performed:
40V 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: 256 MB NAND: 256 MiB Using default environment MUSB: using high speed In: serial usbtty Out: serial usbtty Err: serial usbtty Board revision C Serial #7f6800030000000004013f780601a005 Hit any key to stop autoboot: 0 reading boot.scr DRAM: 256 MB Board revision C Running bootscript from mmc ... ## Executing script at 82000000 reading x-load.bin.ift 20392 bytes read ***** NAND will be Flashed with new x-loader and u-boot ***** ***** Replacing x-load ***** device 0 whole chip HW ECC selected NAND erase: device 0 offset 0x0, size 0x80000 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 ***** Replacing u-boot ***** reading u-boot.bin 727684 bytes read device 0 whole chip SW ECC selected NAND erase: device 0 offset 0x80000, size 0x160000 Erasing at 0x1c0000 -- 100% complete. OK NAND write: device 0 offset 0x80000, size 0x160000 1441792 bytes written: OK ***** Erasing environment settings ***** device 0 whole chip NAND erase: device 0 offset 0x160000, size 0x20000 Erasing at 0x160000 -- 100% complete. OK reading uImage.bin 2578012 bytes read ***** Kernel: /dev/mmcblk0p1/uImage.bin ***** reading ramdisk.gz 33554432 bytes read ***** RootFS: /dev/mmcblk0p1/ramdisk.gz ***** Other tests will continue after Kernel booting, If uImage.bin and ramdisk.gz are on MMC card then kernel will boot as shown below ....
## 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. Linux version 2.6.28-omap1 (root@tiioss) (gcc version 4.2.1 (CodeSourcery Source ry G++ Lite 2007q3-51)) #2 Thu Feb 19 12:45:34 IST 2009 CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c5387f CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache Machine: OMAP3 Beagle Board Memory policy: ECC disabled, Data cache writeback OMAP3430 ES3.0 SRAM: Mapped pa 0x40200000 to va 0xd7000000 size: 0x100000 Reserving 15728640 bytes SDRAM for VRAM Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024 Kernel command line: console=ttyS2,115200n8 console=tty0 root=/dev/ram0 rw ramdi sk_size=32768 initrd=0x81600000,32M < followed by other messages till it reaches console ...>
.-------.
| | .-.
| | |-----.-----.-----.| | .----..-----.-----.
| | | __ | ---'| '--.| .-'| | |
| | | | | |--- || --'| | | ' | | | |
'---'---'--'--'--. |-----''----''--' '-----'-'-'-'
-' |
'---'
The Angstrom Distribution beagleboard ttyS2
Angstrom 2008.1-test-20090127 beagleboard ttyS2
beagleboard login:
Type root and <hit a ENTER Key> Continue Board Validation
1. Select the Linux.inf as the driver, if you don't find it automatically, then you can copy one from Linux Kernel Source folder (2.6_kernel_revb-v2.tar.gz), from the path "2.6_kernel/Documentation/usb/linux.inf" 2. On the Windows PC, bring up Network Connections and look for the Device Name: Linux USB Ethernet/RNDIS Gadget. Right-mouse click for Properties. Scroll down to Internet Protocol (TCP/IP), select it, and press the Properties button. 3. Select an IP address close to the one selected for the Beagle Board. This example uses an IP address of 192.168.1.5 and a Subnet mask of 255.255.255.0. 4. Configure a static IP address for Beagle Board with the ifconfig command. The example below configures an IP address of 192.168.1.1 with a subnet mask of 255.255.255.0. [root@beagleboard mmc]# ifconfig usb0 192.168.1.1 netmask 255.255.255.0 5. On the terminal emulator connected to the Beagle Board use ping to test the connection. Press the Ctrl-C buttons to terminate ping. [root@beagleboard mmc]# ping 192.168.1.5 PING 192.168.1.5 (192.168.1.5): 56 data bytes 64 bytes from 192.168.1.5: seq=0 ttl=128 time=0.885 ms 64 bytes from 192.168.1.5: seq=1 ttl=128 time=0.977 ms 64 bytes from 192.168.1.5: seq=2 ttl=128 time=0.977 ms do a [root@beagleboard mmc]#ifconfig usb0 down [root@beagleboard mmc]# svideo [root@beagleboard mmc]# mplayer /sample_video.avi NOTE: The Video sample has been downloaded from https://garage.maemo.org/tracker/download.php/54/269/2380/258/bug.avi Should display a cartoon video on DVI and S-Video, Audio will be on audio-out (speakers) [root@beagleboard /]# mount -t vfat /dev/mmcblk0p1 /mnt [root@beagleboard /]# cd /mnt Make Sure your player is running and Audio Line in is connected to board. [root@beagleboard mmc]# arecord -t wav -c 2 -r 44100 -f S16_LE -v k Following output is expected on Console Recording WAVE 'k' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo Plug PCM: Hardware PCM card 0 'TWL4030' device 0 subdevice 0 Its setup is: stream : CAPTURE access : RW_INTERLEAVED format : S16_LE subformat : STD channels : 2 rate : 44100 exact rate : 44100 (44100/1) msbits : 16 buffer_size : 32768 period_size : 2048 period_time : 46439 tick_time : 7812 tstamp_mode : NONE period_step : 1 sleep_min : 0 avail_min : 2048 xfer_align : 2048 start_threshold : 1 stop_threshold : 32768 silence_threshold: 0 silence_size : 0 boundary : 1073741824 When ever you think you want to stop just press CONTRL+C [root@beagleboard mmc]# aplay -t wav -c 2 -r 44100 -f S16_LE -v k Audio should be heard on Speakers, Following output is expected on console Playing WAVE 'k' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo Plug PCM: Hardware PCM card 0 'TWL4030' device 0 subdevice 0 Its setup is: stream : PLAYBACK access : RW_INTERLEAVED format : S16_LE subformat : STD channels : 2 rate : 44100 exact rate : 44100 (44100/1) msbits : 16 buffer_size : 32768 period_size : 2048 period_time : 46439 tick_time : 7812 tstamp_mode : NONE period_step : 1 sleep_min : 0 avail_min : 2048 xfer_align : 2048 start_threshold : 32768 stop_threshold : 32768 silence_threshold: 0 silence_size : 0 boundary : 1073741824 This tests validates read/write to MMC/SD card as the audio data is being written and read from MMC.
[root@beagleboard mmc]# cd /
[root@beagleboard mmc]# umount /mnt[root@beagleboard mmc]# evtest /dev/input/event2 Press a Key on USB KeyBoard, Example if "a" is pressed the following output is seen on Console: Event: time 1657.754638, type 1 (Key), code 30 (A), value 1 Event: time 1657.754638, -------------- Report Sync ------------ Event: time 1657.964599, type 1 (Key), code 30 (A), value 0 Event: time 1657.964599, -------------- Report Sync ------------ Press CONTROL+C to come out of this test [root@beagleboard mmc]# evtest /dev/input/event4 Press the Mouse button and observe the screen, Example if Left button is pressed and released the following lines should get displayed on console Event: time 1871.724792, -------------- Report Sync ------------ Event: time 1873.804687, type 1 (Key), code 272 (LeftBtn), value 1 Event: time 1873.804687, -------------- Report Sync ------------ Event: time 1873.964660, type 1 (Key), code 272 (LeftBtn), value 0 Event: time 1873.964660, -------------- Report Sync ------------ Moving the Mouse also results in Console messages Event: time 1959.120635, -------------- Report Sync ------------ Event: time 1959.130676, type 2 (Relative), code 0 (X), value -21 Event: time 1959.130676, -------------- Report Sync ------------ Event: time 1959.140625, type 2 (Relative), code 0 (X), value -16 Press CONTROL+C to come out of this test # root@beagleboard:~# reboot
While kernel boots:
- Connect a HUSB HUB with Mini A connector to USB OTG port on beagleboard
- Connect a USB Keyboard, Mouse to USB HUB
*Kernel boots*[root@beagleboard mmc]# evtest /dev/input/event2 Press a Key on USB KeyBoard, Example if "a" is pressed the following output is seen on Console: Event: time 1657.754638, type 1 (Key), code 30 (A), value 1 Event: time 1657.754638, -------------- Report Sync ------------ Event: time 1657.964599, type 1 (Key), code 30 (A), value 0 Event: time 1657.964599, -------------- Report Sync ------------ Press CONTROL+C to come out of this test [root@beagleboard mmc]# evtest /dev/input/event4 Press the Mouse button and observe the screen, Example if Left button is pressed and released the following lines should get displayed on console Event: time 1871.724792, -------------- Report Sync ------------ Event: time 1873.804687, type 1 (Key), code 272 (LeftBtn), value 1 Event: time 1873.804687, -------------- Report Sync ------------ Event: time 1873.964660, type 1 (Key), code 272 (LeftBtn), value 0 Event: time 1873.964660, -------------- Report Sync ------------ Moving the Mouse also results in Console messages Event: time 1959.120635, -------------- Report Sync ------------ Event: time 1959.130676, type 2 (Relative), code 0 (X), value -21 Event: time 1959.130676, -------------- Report Sync ------------ Event: time 1959.140625, type 2 (Relative), code 0 (X), value -16 Press CONTROL+C to come out of this test [root@beagleboard mmc]# ifconfig eth0 <ipaddress> Example: [root@beagleboard mmc]# ifconfig eth0 172.24.191.49 up <6>eth0: link up, 10Mbps, half-duplex, lpa 0x0020 eth0: link up, 10Mbps, half-duplex, lpa 0x0020 [root@beagleboard mmc]# ping 172.24.191.1 PING 172.24.191.1 (172.24.191.1): 56 data bytes 64 bytes from 172.24.191.1: seq=0 ttl=64 time=2.136 ms 64 bytes from 172.24.191.1: seq=1 ttl=64 time=1.068 ms 64 bytes from 172.24.191.1: seq=2 ttl=64 time=1.038 ms Other Tests
OMAP3 beagleboard.org # ibus 2 0x64 OMAP3 beagleboard.org # imd 0x50 0 100 Should get some thing similar header: 0000: 00 ff ff ff ff ff ff 00 10 ac 24 40 5a 39 41 41 ..........$@Z9AA 0010: 1f 11 01 03 80 22 1b 78 ee ae a5 a6 54 4c 99 26 .....".x....TL.& 0020: 14 50 54 a5 4b 00 71 4f 81 80 01 01 01 01 01 01 .PT.K.qO........ 0030: 01 01 01 01 01 01 30 2a 00 98 51 00 2a 40 30 70 ......0*..Q.*@0p 0040: 13 00 52 0e 11 00 00 1e 00 00 00 ff 00 50 4d 30 ..R..........PM0 0050: 36 31 37 38 32 41 41 39 5a 0a 00 00 00 fc 00 44 61782AA9Z......D 0060: 45 4c 4c 20 31 37 30 38 46 50 0a 20 00 00 00 fd ELL 1708FP. .... 0070: 00 38 4c 1e 51 0e 00 0a 20 20 20 20 20 20 00 36 .8L.Q... .6 Note the words "DELL 1708FP" which is the ID of the monitor.
OMAP3 beagleboard.org # nand unlock OMAP3 beagleboard.org # nand erase Will delete complete NAND
NOTE: Copy x-load.bin.ift and u-boot.bin onto MMC as mentioned above
Boot the Board with MMC/SD card (should use MLO and u-boot.bin)
Power the board by pressing the user buttonfatload mmc 0 80200000 x-load.bin.ift nand unlock nandecc hw nand erase 0 80000 nand write 80200000 0 20000 nand write 80200000 20000 20000 nand write 80200000 40000 20000 nand write 80200000 60000 20000 fatload mmc 0 80200000 u-boot.bin nand unlock nandecc sw nand erase 80000 160000 nand write 80200000 80000 160000
arecord -t wav -c 2 -r 8000 -f S16_LE -v /mnt/mmc/rec_8000.dat arecord -t wav -c 2 -r 11025 -f S16_LE -v /mnt/mmc/rec_11025.dat arecord -t wav -c 2 -r 12000 -f S16_LE -v /mnt/mmc/rec_12000.dat arecord -t wav -c 2 -r 16000 -f S16_LE -v /mnt/mmc/rec_16000.dat arecord -t wav -c 2 -r 22050 -f S16_LE -v /mnt/mmc/rec_22050.dat arecord -t wav -c 2 -r 24000 -f S16_LE -v /mnt/mmc/rec_24000.dat arecord -t wav -c 2 -r 32000 -f S16_LE -v /mnt/mmc/rec_32000.dat arecord -t wav -c 2 -r 44100 -f S16_LE -v /mnt/mmc/rec_44100.dat arecord -t wav -c 2 -r 48000 -f S16_LE -v /mnt/mmc/rec_48000.dat aplay -t wav -c 2 -r 8000 -f S16_LE -v /mnt/mmc/rec_8000.dat aplay -t wav -c 2 -r 11025 -f S16_LE -v /mnt/mmc/rec_11025.dat aplay -t wav -c 2 -r 12000 -f S16_LE -v /mnt/mmc/rec_12000.dat aplay -t wav -c 2 -r 16000 -f S16_LE -v /mnt/mmc/rec_16000.dat aplay -t wav -c 2 -r 22050 -f S16_LE -v /mnt/mmc/rec_22050.dat <so on>
setenv bootargs console=ttyS2,115200n8 ramdisk_size=32768 root=/dev/ram0 rw rootfstype=ext2 initrd=0x81600000,32M omapfb.video_mode=1280x720MR-48@60 mmcinit;fatload mmc 0 0x80300000 uImage.bin;fatload mmc 0 0x81600000 ramdisk.gz;bootm 0x80300000; These might work as well, setenv bootargs console=ttyS2,115200n8 ramdisk_size=32768 root=/dev/ram0 rw rootfstype=ext2 initrd=0x81600000,32M omapfb.video_mode=720x480MR-16@60 setenv bootargs console=ttyS2,115200n8 ramdisk_size=32768 root=/dev/ram0 rw rootfstype=ext2 initrd=0x81600000,32M omapfb.video_mode=720x576MR-12@60 setenv bootargs console=ttyS2,115200n8 ramdisk_size=32768 root=/dev/ram0 rw rootfstype=ext2 initrd=0x81600000,32M omapfb.video_mode=1280x720MR-110@60 |
Sign in to add a comment
These bootargs worked for my HDTV with this kernel and file system: console=ttyS2,115200 console=tty0 root=/dev/ram0 rw ramdisk=32768 initrd=0x81600000,32M video=omapfb.video_mode=1280x720M-24@60
The video is black-and-white for me.
Here are my bootargs: console=ttyS2,115200n8 omapfb.video_mode=1280x720MR-24@60 omapfb.debug=y root=/dev/ram0 rw ramdisk_size=32768 initrd=0x81600000,32M
I had major issues getting the DVI to work... The debug stuff can be removed now I believe.
Being a Linux guy, I used steps similar to http://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat to make the SD card. When I powered the board from a Linux USB port, I got the error "Unknown command 'T+GCAP' - try 'help'", even though I was using a serial cable. This is due to u-boot supporting USB CDC ACM protocol and NetworkManager? probing for an attached modem by sending the AT command "AT+GCAP", which interrupts the boot process. I ignored the problem (after failing to figure out how to get NetworkManager? from probing) and just entered 'boot' at the u-boot prompt.
I get overrun errors when recording.
To test the user button: root@beagleboard:~# evtest /dev/input/event1
The EDID commands still don't work for me.
We need to eliminate the need to do "save as..." and change the name. A single utility is required as well.
got error when trying to get u-boot code (x-load and kernel are working fine):
git clone http://git.gitorious.org/beagleboard/mainline.git/
...
walk 7309612797ed5e6b3b20027e28bca970b4f6b8fd
walk 0b666f81da14bf46cada222856762f7fd6641c26
warning: remote HEAD refers to nonexistent ref, unable to checkout.
is "git clone http://git.gitorious.org/beagleboard/mainline.git/" the right way?
Can I do all these procedure on Rev B5 Board?
I got the following errors on rev B6, any ideas how to fix this? Thanks.
uncorrectable error : <3>end_request: I/O error, dev mtdblock0, sector 0 Buffer I/O error on device mtdblock0, logical block 0 uncorrectable error : <3>end_request: I/O error, dev mtdblock0, sector 8 Buffer I/O error on device mtdblock0, logical block 1 uncorrectable error : <3>end_request: I/O error, dev mtdblock0, sector 16 Buffer I/O error on device mtdblock0, logical block 2 uncorrectable error : <3>end_request: I/O error, dev mtdblock0, sector 24 Buffer I/O error on device mtdblock0, logical block 3 uncorrectable error : <3>end_request: I/O error, dev mtdblock0, sector 0 Buffer I/O error on device mtdblock0, logical block 0
On my RevC board, I thought I would attempt to update u-boot, but nand unlock returns a Usage message:
version info from console during power-on:
Also, on my RevC board, I've never been able to get Windows to correctly install the needed drivers for "U-Boot 2009.01-dirty". I keep getting "new hardware found" (and it is ignoring the linux.inf and gserial.inf as valid drivers), except once during validation (with User button held during power-on) when it identified as "OMAP3530". The last several times I've tried to install drivers (choosing the file manually thru the "have disk" dialog, I've been prompted for the location of usbser.sys. I've starting using an external power source instead of the USB port, as I don't really need the network routing thru my desktop.
Is anyone else seeing similar or do I have issues with my Windows USB drivers?
WARNING! Don't use this filesystem for anything but validation. Opkg is not configured and you will be dead in the water. Go here: http://beagleboard.org/demo/angstrom/
(from the mavens on irc://freenode/beagle)
Link for "Recommended HP USB Disk Storage Format Tool 2.0.6" is dead. Here is another one.
http://downloads.pcworld.com/pub/new/utilities/peripherals/SP27608.exe
On my RevC BB with u-boot: U-Boot 2009.01-dirty (Feb 19 2009 - 12:23:21) I cannot validate the EDID as per instructions above.
The "ibus 2 0x64" command issues a warning as it does NOT take two arguments - it only expects the "2" not the 0x64.
If I attempt to issue the commands: ibus 2 and imd 0x50 0 100 I get timeout/read errors.
It appears that the EDID instructions above are NOT valid for the RevC BB.
My terminal screen does not display any information below "Press CTRL-A Z for help on special keys." I am using a minicom 2.3-rc1
In fact, it displays "Offline" at the bottom of the window. Yes, the monitor screen for the beagle board does display the beagle board logo.
Has anyone had this issue?
I spent a very long time playing with the NAND flash and u-boot to try to get my SD card to properly auto-boot.
If you plan to use u-boot from NAND, you must remove u-boot.bin from the SD card.
The u-boot load priority should likely be included in the documentation someplace.
http://selfdestruct.net/misc/usbboot/SP27213.exe link is broken. There are some other Windows formatting utilities that work. Need to share a good one.
How to configure and check if wi-fi is working using wireless usb adapter (i.e. dongle)
I was able to resolve the arecord overrun errors (reported by jason on 2/21/09) by changing the destination source file to media/ram/k. I executed the command from the /mnt directory.
I could also copy the file back to SD card and playback fine. Just seems like record can't keep up with writing to SD card.
I posted additional comments/notes/feedback to the newsgroup. Please see post at: http://groups.google.com/group/beagleboard/browse_thread/thread/9c8750e67dbf398a/6d8268322f3d7530#6d8268322f3d7530
I followed the instructions given here and I have been able to successfully been able to restore my NAND flash on a rev C3 beagleboard. However, I am seeing the following output at the end of the restore step which says that it could not read normal.scr. I also noticed that it does not appear to be writing the uImage or ramdisk images from the SD card and placing them into NAND.
Begin OutputOMAP3 beagleboard.org # 40V 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: 256 MB NAND: 256 MiB Using default environment MUSB: using high speed In: serial usbtty Out: serial usbtty Err: serial usbtty Board revision C Serial #5ac400030000000004013f8901001001 Hit any key to stop autoboot: 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 0x60000 -- 100% complete. OK NAND write: device 0 offset 0x0, size 0x20000
- 1072 bytes written: OK
NAND write: device 0 offset 0x20000, size 0x20000- 1072 bytes written: OK
NAND write: device 0 offset 0x40000, size 0x20000- 1072 bytes written: OK
NAND write: device 0 offset 0x60000, size 0x20000- 1072 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 0x1c0000 -- 100% complete. OK NAND write: device 0 offset 0x80000, size 0x160000- 41792 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 Invalid FAT entry Unable to read "normal.scr" from mmc 0:1 End OutputI also noticed that after the process was done the kernel did not boot as mentioned. My environment was left as:
OMAP3 beagleboard.org # printenv bootdelay=10 baudrate=115200 loadaddr=0x80200000 rdaddr=0x81600000 console=ttyS2,115200n8 optargs= mmcargs=setenv bootargs console=${console} ${optargs} root=/dev/mmcblk0p2 rw rot ramargs=setenv bootargs console=${console} ${optargs} root=/dev/ram0 rw ramdiskM ubifsargs=setenv bootargs console=${console} ${optargs} root=ubi0:beagleroot ubs jffs2args=setenv bootargs console=${console} ${optargs} root=/dev/mtdblock4 rw 2 loadbootscript=fatload mmc 0 ${loadaddr} boot.scr bootscript=echo Running bootscript from mmc ...; autoscr ${loadaddr} loaduimage=fatload mmc 0 ${loadaddr} uImage.bin loadramdisk=fatload mmc 0 ${rdaddr} ramdisk.gz ramboot=echo Booting from ramdisk.gz ...; run ramargs; bootm ${loadaddr} mmcboot=echo Booting from mmc ...; run mmcargs; bootm ${loadaddr} nandboot=echo Booting from nand ...; run jffs2args; nand read ${loadaddr} 28000} usbtty=cdc_acm stdout=serial,usbtty stdin=serial,usbtty stderr=serial,usbtty serial=5ac400030000000004013f8901001001 bootargs=console=ttyS2,115200n8 console=tty0 root=/dev/mmcblk0p2 rootwait rootf0 filesize=435D8 bootcmd=mmcinit; fatload mmc 0 0x80300000 uImage; bootm 0x80300000
I am able to save new environment variables to the NAND and the board will boot into u-boot, but I am wondering why my kernel image and file system were not written into NAND. Any help would be appreciatI also noticed that after the process was done the kernel did not boot as mentioned. My environment was left as:
OMAP3 beagleboard.org # printenv bootdelay=10 baudrate=115200 loadaddr=0x80200000 rdaddr=0x81600000 console=ttyS2,115200n8 optargs= mmcargs=setenv bootargs console=${console} ${optargs} root=/dev/mmcblk0p2 rw rot ramargs=setenv bootargs console=${console} ${optargs} root=/dev/ram0 rw ramdiskM ubifsargs=setenv bootargs console=${console} ${optargs} root=ubi0:beagleroot ubs jffs2args=setenv bootargs console=${console} ${optargs} root=/dev/mtdblock4 rw 2 loadbootscript=fatload mmc 0 ${loadaddr} boot.scr bootscript=echo Running bootscript from mmc ...; autoscr ${loadaddr} loaduimage=fatload mmc 0 ${loadaddr} uImage.bin loadramdisk=fatload mmc 0 ${rdaddr} ramdisk.gz ramboot=echo Booting from ramdisk.gz ...; run ramargs; bootm ${loadaddr} mmcboot=echo Booting from mmc ...; run mmcargs; bootm ${loadaddr} nandboot=echo Booting from nand ...; run jffs2args; nand read ${loadaddr} 28000} usbtty=cdc_acm stdout=serial,usbtty stdin=serial,usbtty stderr=serial,usbtty serial=5ac400030000000004013f8901001001 bootargs=console=ttyS2,115200n8 console=tty0 root=/dev/mmcblk0p2 rootwait rootf0 filesize=435D8 bootcmd=mmcinit; fatload mmc 0 0x80300000 uImage; bootm 0x80300000
I am able to save new environment variables to the NAND and the board will boot into u-boot, but I am wondering why my kernel image and file system were not written into NAND. Any help would be appreciated
I got these major errors. does any one know any solution about this
hwclock: can't open /dev/misc/rtc no such file or directory buffer i/o error on device mtdblock1, logical block 21 uncorrectable error dev mtdblock1, sector 168