2011-08-23 07:50:53 Linux Kernel debugging with volatile U-Boot
Peter Kampmann (GERMANY)
the custom board with a BF537 i am working on is stuck while booting uclinux
## Booting kernel from Legacy Image at 00c00000 ...
Created: 2011-08-23 11:29:43 UTC
Image Type: Blackfin Linux Kernel Image (gzip compressed)
Data Size: 3062903 Bytes = 2.9 MiB
Load Address: 00001000
Entry Point: 002b5f30
Verifying Checksum ...
Uncompressing Kernel Image ...
Starting Kernel at = 002b5f30
I've read that normally I should debug this issue using the "Linux post mortem analysis" /https://docs.blackfin.uclinux.org/doku.php?id=linux-kernel:debug:post_mortem), as far as I understand those, I need a u-boot stored in flash of the system
in order to perform these approaches.
Unfortunately, my system does not have any flash and I need to load the U-Boot via UART. The ucLinux is loaded via
tftp. So is there another way to come across the possible issues I have ?
Here is my bdinfo:
U-Boot = U-Boot 2010.06 (ADI-2010R1-RC2) (Aug 23 2011 - 11:52:48)
CPU = bf537-0.3
Board = dfki_seegrip
VCO = 500 MHz
CCLK = 500 MHz
SCLK = 100 MHz
boot_params = 0x00000000
memstart = 0x00000000
memsize = 0x01000000
flashstart = 0x00000000
flashsize = 0x00000000
flashoffset = 0x00000000
ethaddr = 46:71:63:24:36:37
ip_addr = 192.168.0.15
baudrate = 57600 bps
And here are the bootargs, earlyprintk is enabled.
bootargs=root=/dev/mtdblock0 rw clkin_hz=25000000 earlyprintk=serial,uart0,57600 console=ttyBF0,57600
I also attached the output of make bugreport to this post. Hope that anybody can give me some hints to this issue.
2011-08-23 23:55:32 Re: Linux Kernel debugging with volatile U-Boot
Sonic Zhang (CHINA)
What do you change to the bf537-stamp default kernel config?
Please try the prebuilt bf537-stamp kernel uImage from the 2010R1 replease page on your board.