Hallo Sebastian, On Thu, Nov 13, 2014 at 12:31:08PM +0100, Sebastian Hesselbarth wrote: > >I don't manage to boot via UART. The usual outcome is: > > > >Sending boot message. Please reboot the target...\ > >Sending boot image... > > 0 % [......................................................................] > > 2 % [......................................................................] > > 5 % [......................................................................] > > 7 % [......................................................................] > > 10 % [......................................................................] > > 13 % [..................................xmodem: Connection timed out > > > >If I try to boot a barebox-globalscale-mirabox.img (provided by > >ezequielg in #mvlinux), I get: > > > >$ scripts/kwboot -b ../barebox-globalscale-mirabox.img -t /dev/ttyUSB1 > >Sending boot message. Please reboot the target...\ > >Sending boot image... > > 0 % [......................................................................] > > 5 % [......................................................................] > > 10 % [......................................................................] > > 14 % [......................................................................] > > 19 % [......................................................................] > > 24 % [.................................DDR3 Training Sequence - Ver 2.1.6 > >DDR3 Training Sequence - Number of DIMMs detected: 1 > >+xmodem: Connection timed out > > That indeed is strange and indicates some general problem. Can you retry > with setting the baudrate to 115200 (-b 115200 IIRC). Doesn't change anything. In fact the tty is already configured for 115200 Baud. And I would expect that on a mismatch it wouldn't always die just after the header is uploaded. Just noticed that my binary.0 was corrupted as I extraced it from a nand dump that also included the oob area ... With a proper image I get barebox up now. > >And funny enough, during testing I added > > > > select(fd + 1, &rfds, NULL, NULL, &tv); > > > >to kwboot_tty_recv after the read, this results reproduibly into a > >single NAK and "BootROM: Invalid header checksum". This is still not explained. I would have expected that this select doesn't do anything noticable on the remote end. > >When booting from nand (as shipped by Netgear) the output starts with: > > You need to set boot source byte to UART (0x52 IIRC). Otherwise the NAND Just for the log: UART = 0x69. Best regards Uwe -- Pengutronix e.K. | Uwe Kleine-König | Industrial Linux Solutions | http://www.pengutronix.de/ | _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
