Joe ZhangNew Member Posts:17
11 Oct 2013 04:54 PM |
|
This post is based on the documentation of "OMAP-L138/AM1808 SOM-M1 U-Boot Labs -Bootloader Documentation".
Up on to finished this lab, the boot up stops at last message:
Uncompressing Linux.............................................................................................................................. done, booting the kernel.
The Steps I did as following:
logic@logic-desktop:~$ minicom -w
Welcome to minicom 2.4
OPTIONS: I18n
Compiled on Jan 25 2010, 07:02:36.
Port /dev/ttyUSB0
Press CTRL-A Z for help on special keys
Booting with TI UBL
Device OPP (300MHz, 1.2V)
U-Boot 2009.11 (May 03 2010 - 15:38:40)
I2C: ready
DRAM: 64 MB
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
ARM Clock : 300000000 Hz
DDR Clock : 132000000 Hz
Invalid MAC address read.
Net: Ethernet PHY: GENERIC @ 0x00
Hit any key to stop autoboot: 0
U-Boot >
U-Boot > setenv dnsip 192.168.111.236
U-Boot > setenv ethaddr 00:08:EE:04:9C:5B
U-Boot > setenv ipaddr 192.168.111.131
U-Boot > setenv netmask 255.255.255.0
U-Boot > setenv serverip 192.168.111.226
U-Boot > saveenv
Saving Environment to SPI Flash...
Erasing SPI flash...Writing to SPI flash...done
U-Boot > ping 192.168.111.189
Using device
host 192.168.111.189 is alive
U-Boot > tftp 0xc0700000 uImage
Using device
TFTP from server 192.168.111.226; our IP address is 192.168.111.131
Filename 'uImage'.
Load address: 0xc0700000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################
done
Bytes transferred = 1913044 (1d30d4 hex)
U-Boot > sf probe 0
8192 KiB M25P64 at 0:0 is now current device
U-Boot > sf erase 0x80000 0x200000
U-Boot > sf write 0xc0700000 0x80000 0x200000
U-Boot > tftp 0xc1180000 ramdisk-base.gz
Using device
TFTP from server 192.168.111.226; our IP address is 192.168.111.131
Filename 'ramdisk-base.gz'.
Load address: 0xc1180000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
###############################
done
Bytes transferred = 3150629 (301325 hex)
U-Boot > sf erase 0x280000 0x400000
U-Boot > sf write 0xc1180000 0x280000 0x40000
U-Boot > sf write 0xc1180000 0x280000 0x400000
U-Boot > setenv bootargs 'mem=32M console=ttyS2,11520n8 root=/dev/ram0 rw initrd=0xc1180000, 4m ip=off'
U-Boot > setenv bootcmd 'sf probe 0; sf read 0xc0700000 0x80000 0x200000; sf read 0xc1180000 0x280000 0x400000; bootm 0xc0700000'
U-Boot > saveenv
Saving Environment to SPI Flash...
Erasing SPI flash...Writing to SPI flash...done
U-Boot > print
bootdelay=3
baudrate=115200
bootfile="uImage"
dnsip=192.168.111.236
ethaddr=00:08:EE:04:9C:5B
stdin=serial
stdout=serial
stderr=serial
ver=U-Boot 2009.11 (May 03 2010 - 15:38:40)
filesize=301325
fileaddr=C1180000
netmask=255.255.255.0
ipaddr=192.168.111.131
serverip=192.168.111.226
bootargs=mem=32M console=ttyS2,11520n8 root=/dev/ram0 rw initrd=0xc1180000, 4m ip=off
bootcmd=sf probe 0; sf read 0xc0700000 0x80000 0x200000; sf read 0xc1180000 0x280000 0x400000; bootm 0xc0700000
Environment size: 481/65532 bytes
U-Boot > run bootcmd
8192 KiB M25P64 at 0:0 is now current device
## Booting kernel from Legacy Image at c0700000 ...
Image Name: Linux-2.6.32-rc6
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1912980 Bytes = 1.8 MB
Load Address: c0008000
Entry Point: c0008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux.............................................................................................................................. done, booting the kernel.
|
|
|
|
steven.eckhoffBasic Member Posts:192
14 Oct 2013 01:01 PM |
|
Joe, Are you following the steps from section 5? I am seeing some differences in the U-Boot environment. Before modifying the instructions for your needs, you should verify that the steps work with the static software images.
|
|
|
|
Joe ZhangNew Member Posts:17
14 Oct 2013 01:29 PM |
|
Steven, I did follow section 5. According to this section, the ompal138 xperimenter kit only needs setenv dlbuf 0xc0400000 and setenv kerneladdr 0x00080000. these two parameters, I am not should how much they related to boot up, but I do add them and still have same result that stops booting the kernel. Can you point to me which environments are different than what you think they should be? Thanks
|
|
|
|
steven.eckhoffBasic Member Posts:192
14 Oct 2013 02:22 PM |
|
Joe, The writer of these labs provided a static software image, so I assume that you would also need to use the same U-Boot env as displayed in the screen shots. The are several places where yours differs. For example, your bootcmd is set differently. When doing this make sure that everything is consistent with the screen shots and output highlighted in the document.
|
|
|
|
Joe ZhangNew Member Posts:17
14 Oct 2013 05:17 PM |
|
Steven, I double check the last screenshot on the document (page 37, just above 7.6 Boot the Linux Kernel) with my one, the difference between them there are 3 SPACE in my and address 'C' is low case, I fixed these and still have same result that stops booting Kernel. What else you have seen? Thank you
|
|
|
|
steven.eckhoffBasic Member Posts:192
14 Oct 2013 05:55 PM |
|
Joe, Okay, based on your previous comment, I thought you were working in section 5. Your steps for section 7 look good. I have only checked them up until the following because I am pretty sure this is your issue. setenv bootargs 'mem=32M console=ttyS2,11520n8 root=/dev/ram0 rw initrd=0xc1180000, 4m ip=off' the baud rate that you are telling the kernel to use is wrong. You have: 11520n8 It should be: 115200n8 Likely, the kernel is booting, but not able to output to the serial console. When I see the below output, I usually suspect that there is an error in the bootargs. I checked and missed it the first time. Keep this in mind next time you see the following: Starting kernel ... Uncompressing Linux.............................................................................................................................. done, booting the kernel.
|
|
|
|
Joe ZhangNew Member Posts:17
14 Oct 2013 05:58 PM |
|
Hi Steven, I am adding my latest environment of u-boot here, which I think match the last screen shot of the document. U-Boot > print bootdelay=3 baudrate=115200 bootfile="uImage" dnsip=192.168.111.236 ethaddr=00:08:EE:04:9C:5B filesize=301325 fileaddr=C1180000 netmask=255.255.255.0 ipaddr=192.168.111.131 serverip=192.168.111.226 bootcmd=sf probe 0; sf read 0xC0700000 0x80000 0x200000;sf read 0xC1180000 0x280000 0x400000;bootm 0xC0700000 bootargs=mem=32M console=ttyS2,11520n8 root=/dev/ram0 rw initrd=0xC1180000, 4m ip=off stdin=serial stdout=serial stderr=serial ver=U-Boot 2009.11 (May 03 2010 - 15:38:40) Environment size: 479/65532 bytes
|
|
|
|
Joe ZhangNew Member Posts:17
14 Oct 2013 08:04 PM |
|
Hi Steven, Thank you for captured the mistake. I do fix it and still have same out and stop booting I really don't see any wrong again. Would you please, help me again? Thank you Joe
|
|
|
|
steven.eckhoffBasic Member Posts:192
15 Oct 2013 09:00 AM |
|
Joe, I still see the error in the environment you posted.
|
|
|
|
Joe ZhangNew Member Posts:17
15 Oct 2013 12:19 PM |
|
O, you may look at my older environments. Here is new one. U-Boot > print bootdelay=3 baudrate=115200 bootfile="uImage" dnsip=192.168.111.236 ethaddr=00:08:EE:04:9C:5B filesize=301325 fileaddr=C1180000 netmask=255.255.255.0 ipaddr=192.168.111.131 serverip=192.168.111.226 bootcmd=sf probe 0; sf read 0xC0700000 0x80000 0x200000;sf read 0xC1180000 0x280000 0x400000;bootm 0xC0700000 bootargs=mem=32M console=ttyS2,115200n8 root=/dev/ram0 rw initrd=0xC1180000, 4m ip=off stdin=serial stdout=serial stderr=serial ver=U-Boot 2009.11 (May 03 2010 - 15:38:40) Environment size: 480/65532 bytes
|
|
|
|
Joe ZhangNew Member Posts:17
21 Oct 2013 12:42 PM |
|
Steven, You asked me to post question in this forums, but It has been pasted 6 days. I still don't get your reply. I do ask same question on TI's 2e2. I got reply to confirm the bootargs seems correct. So, hope you can work on your side to see what is the real problem. Thank you Joe
|
|
|
|
steven.eckhoffBasic Member Posts:192
21 Oct 2013 01:08 PM |
|
Joe, We will need to spend some time examining your setup. We can assign a full-time resource on this issue if you purchase a support contract. Otherwise, we will take another look at your setup as soon as we can.
|
|
|
|
Joe ZhangNew Member Posts:17
21 Oct 2013 02:30 PM |
|
Hi Steven, I got a hit from TI's E2E forum and find the baudrate is only half of what it should be. Since I used the image file from LogicPD provided and don't know what source it was based, therefor, I use my own build u-boot and uImage. also made size adjusted. It works now. Thanks Joe
|
|
|
|
steven.eckhoffBasic Member Posts:192
21 Oct 2013 02:51 PM |
|
Joe, I am not sure that I understand your post. The baud rate should be 115200. Will you post the link to the e2e thread, so others can benefit from it?
|
|
|
|
Joe ZhangNew Member Posts:17
|
steven.eckhoffBasic Member Posts:192
21 Oct 2013 04:22 PM |
|
Joe,
I went through the threads that you mentioned[1][2]. In the second link, the one suggested to you today, it sounds like they were having an issue with the PLL and the baudrate not being set up correctly.
Did you check your baud rate by scoping the TX line using infinite persistence?
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
Linux version
Joe, will you also tell us what the baud rate setting is in your terminal emulator?
I have also included in the links, a link [3] to a TI wiki page that helps troubleshoot these types of issues.
[1] http://e2e.ti.com/support...1038340.aspx#1038340
[2] http://e2e.ti.com/support...s/f/42/t/139578.aspx
[3] http://processors.wiki.ti...ooting_the_kernel.22
|
|
|
|
steven.eckhoffBasic Member Posts:192
21 Oct 2013 04:23 PM |
|
Joe,
Do you have a screen shot of this waveform?
|
|
|
|
Joe ZhangNew Member Posts:17
21 Oct 2013 04:36 PM |
|
Yes, from [1][2] do help me what I should look for the problem. I do use logic analysis to find out the baud rate. It is very easy to find the plus is twice longer than the working plus( 115200). Since I am done with this problem, I don't keep the waveform or to re-generate it. I already change my system back to normal status. That is, I removed my probing already. Thank you Joe
|
|
|
|
steven.eckhoffBasic Member Posts:192
21 Oct 2013 05:50 PM |
|
Joe,
Okay I see the same issue that you had using the uImage from the U-Boot lab files. Using infinite persistence on my scope I can gather what the bit times are. The only problem here is that after the "Uncompressing Linux" message I do not see any UART activity. The bit times look correct while the "Uncompressing Linux" message is printed. The bit time is 9us = 1/115200.
Since I am unable to rebuild under the same environment, I am unable to debug this any further. We will update the images that come with the U-Boot labs.
|
|
|
|
Joe ZhangNew Member Posts:17
21 Oct 2013 06:56 PM |
|
Steven, I don't do infinite sampling the serial data, I only started to captured once I see "Uncompressing Linux" message shows up. I do repeat a few times to capture it. It is good news that you will update the U-Boot labs. Thank you Joe
|
|
|
|