2009-09-30 04:03:21 boot error
Daniele Pagani (ITALY)
Message: 80705
Dear sirs,
I'm moving my development tool from one pc to another.
Pc source:
uclinux revision 8812
linux 2.6.x revision 7258
toolchain:
blackfin-toolchain-09r1-2
blackfin-toolchain-uclibc-default-09r1-2
I have only one custom board, with BF537.
If I compile the image, it works fine, kernel starts, my application works fine and so on.
Pc destination:
uclinux revision 8915
linux 2.6.x revision 7527
toolchain:
blackfin-toolchain-09r1-2
blackfin-toolchain-uclibc-default-09r1-2
Same board, same u-boot.
OpenSuse 11.1 for Pc source and Pc destination.
If I compile the image, then the system doesn't start.
If I try a:
iminfo 0x20040000 in u-boot, then, I have:
Image Name: bf537-2.6.31.1-ADI-2010R1-pre
Created: 2009-09-30 6:45:17 UTC
Image Type: Blackfin Linux Kernel Image (gzip compressed)
Data Size: 2423584 Bytes = 2.3 MB
Load Address: 00001000
Entry Point: 001a0ef4
Verifying Checksum ... OK
Then, if I do a iminfo with the right kernel, I have:
bfin> iminfo 0x20040000
## Checking Image at 20040000 ...
Image Name: bf537-2.6.30.5-ADI-2010R1-pre
Created: 2009-09-29 15:28:11 UTC
Image Type: Blackfin Linux Kernel Image (gzip compressed)
Data Size: 2552646 Bytes = 2.4 MB
Load Address: 00001000
Entry Point: 0019aeb4
Verifying Checksum ... OK
I see that I have a different Entry Point.
I post also my u-boot settings:
printenv
bootdelay=5
baudrate=115200
loads_echo=1
ipaddr=192.168.0.15
serverip=192.168.0.2
rootpath=/romfs
gatewayip=192.168.0.1
netmask=255.255.255.0
hostname=bf537-stamp
loadaddr=0x1000000
ubootfile=u-boot.bin
update=tftp $(loadaddr) $(ubootfile);protect off 0x20000000 0x2003FFFF;erase 0x20000000 0x2003FFFF;cp.b $(loadaddr) 0x20000000 $(filesize)
addip=set bootargs $(bootargs) ip=$(ipaddr):$(serverip):$(gatewayip):$(netmask):$(hostname):eth0:off
ramargs=set bootargs root=/dev/mtdblock0 rw earlyprintk=serial,uart0,115200 console=ttyBF0,115200
ramboot=tftp $(loadaddr) uImage;run ramargs;run addip;bootm
nfsargs=set bootargs root=/dev/nfs rw nfsroot=$(serverip):$(rootpath),tcp,nfsvers=3
nfsboot=tftp $(loadaddr) vmImage;run nfsargs;run addip;bootm
flashboot=bootm 0x20100000
ethaddr=06:35:03:50:A0:A4
ethact=Blackfin EMAC
boot=bootm 0x20040000
bootcmd=bootm 0x20040000
bootargs=root=/dev/mtdblock0 rw earlyprintk=serial,uart0,115200 console=ttyBF0,115200 max_mem=32M mem=28M
stdin=serial
stdout=serial
stderr=serial
Environment size: 1014/8188 bytes
bfin>
Can somebody suggest me something?
Best regards,
Daniele.
TranslateQuoteReplyEditDelete
2009-09-30 04:16:52 Re: boot error
Mike Frysinger (UNITED STATES)
Message: 80707
the different entry point really doesnt matter. it'll change everytime a config option changes as it's in the middle of dynamic code (like it should be).
looks like you're trying to use trunk. it's known to be a bit unstable so if you want to do real work, use the 2009R1 branch.
QuoteReplyEditDelete
2009-09-30 04:33:03 Re: boot error
Daniele Pagani (ITALY)
Message: 80709
Ok,
but, see my last message: Message ID: 80198
With 2009R1 branch I've a problem, so I need to use svn version...so, I don't know if is possible to have the same revision on two pc; do I need to copy directory?
Anyway, I think that we can solve the problem. I give you additional information,
"system doesn't work fine" means:
bfin> bootm 0x1000000
## Booting image at 01000000 ...
Image Name: bf537-2.6.31.1-ADI-2010R1-pre
Created: 2009-09-30 6:45:17 UTC
Image Type: Blackfin Linux Kernel Image (gzip compressed)
Data Size: 2423584 Bytes = 2.3 MB
Load Address: 00001000
Entry Point: 001a0ef4
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
Starting Kernel at = 1a0ef4
Then the system is halted.
Could this suggest something?
Regards,
Daniele.
TranslateQuoteReplyEditDelete
2009-09-30 04:43:03 Re: boot error
Mike Frysinger (UNITED STATES)
Message: 80710
you arent comparing the same exact versions of software, so where they're being built really doesnt matter. you're probably hitting a bug that we've already fixed or are in the process of working on. svn trunk is unstable and you shouldnt be using it.
there is no limitation whatsoever in any of the software from us in terms of having multiple versions on the same machine or across different machines. if you know what you're doing, you can easily have multiple toolchains/kernels/uclinux-dists/etc... building simultaneously.
QuoteReplyEditDelete
2009-09-30 11:26:19 Re: boot error
Frank Van Hooft (CANADA)
Message: 80716
Check your menuconfig settings, and make sure that your console UART port is actually enabled.