Is anyone netbooting a beagle bone black?
I want to test kernel changes that may affect the ability to use
the sd card. I'd like to avoid putting those kernels onto the SD
itself to test them, so I don't have to put the SD into a different
machine to copy a working kernel back every time something bad happens.
So netbooting would be nice. However, I cannot get it to work.
The kernel image used below is known to boot from SD but fails
to boot over the network:
U-Boot# env set ipaddr 217.197.84.45
U-Boot# env set serverip 217.197.84.33
U-Boot# tftpboot 0x80300000 217.197.84.33:bsd.umg
link up on port 0, speed 100, full duplex
Using cpsw device
TFTP from server 217.197.84.33; our IP address is 217.197.84.45
Filename 'bsd.umg'.
Load address: 0x80300000
Loading: #################################################################
#################################################################
###############################################################
822.3 KiB/s
done
Bytes transferred = 2831320 (2b33d8 hex)
U-Boot# bootm 0x80300000
## Booting kernel from Legacy Image at 80300000 ...
Image Name: boot
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2831256 Bytes = 2.7 MiB
Load Address: 80300000
Entry Point: 80300000
Verifying Checksum ... OK
XIP Kernel Image ... OK
OK
Starting kernel ...
data abort
MAYBE you should read doc/README.arm-unaligned-accesses
pc : [<80300008>] lr : [<9ff649ac>]
sp : 9fe42db8 ip : 0000000c fp : 9ff64c08
r10: 9ffaca58 r9 : 00000000 r8 : 9fe42f40
r7 : 00000000 r6 : 00000000 r5 : 80300000 r4 : 9ffad080
r3 : 9fe42fe0 r2 : 80000100 r1 : 00000e05 r0 : 00000000
Flags: nZCv IRQs off FIQs on Mode SVC_32
Resetting CPU ...
resetting ...
