R-Pi Won't boot from SD Card using TFTP

WTware network boot ways - bootable floppy, DOS, PXE-loaders, BootROM chips.
Post Reply
nnh775
Posts: 2
Joined: Fri Feb 08, 2019 8:05 pm

R-Pi Won't boot from SD Card using TFTP

Post by nnh775 » Fri Feb 08, 2019 8:28 pm

I upgraded from 5.8.26 to the latest 5.8.46, and my raspberry's will no longer boot. I'm using SD card for network boot using the wtware tftp server. DHCP is handled by our windows dhcp server: Option 66: 10.10.0.35 - Option 67: 5.8.46\wtware.pxe

The log says file not found: "C:\Program Files (x86)\WTware\TFTPDROOT\890ef7be\autoboot.txt"
I can confirm, that file does not exist. The only files in that folder are:
host
ip
iswtware
platform
version
config.wtc


TFTP Log:

09-19-51-707| [192.168.70.166] RRQ 33 bytes:
09-19-51-707| [192.168.70.166] 00000000: 38 39 30 65 66 37 62 65 2f 73 74 61 72 74 2e 65
09-19-51-707| [192.168.70.166] 00000010: 6c 66 00 6f 63 74 65 74 00 74 73 69 7a 65 00 30
09-19-51-707| [192.168.70.166] 00000020: 00
09-19-51-707| [192.168.70.166] "890ef7be\start.elf": tsize is requested, blksize default.
09-19-51-722| [192.168.70.166] "890ef7be\start.elf": "C:\Program Files (x86)\WTware\TFTPDROOT\5.8.46\pi2\localboot\start.elf".
09-19-51-722| [192.168.70.166] Received opcode ERR.
09-19-51-722| [192.168.70.166] RRQ 36 bytes:
09-19-51-722| [192.168.70.166] 00000000: 38 39 30 65 66 37 62 65 2f 61 75 74 6f 62 6f 6f
09-19-51-722| [192.168.70.166] 00000010: 74 2e 74 78 74 00 6f 63 74 65 74 00 74 73 69 7a
09-19-51-722| [192.168.70.166] 00000020: 65 00 30 00
09-19-51-722| [192.168.70.166] "890ef7be\autoboot.txt": tsize is requested, blksize default.
09-19-51-738| [192.168.70.166] "890ef7be\autoboot.txt": file not found: "C:\Program Files (x86)\WTware\TFTPDROOT\890ef7be\autoboot.txt".
09-19-51-738| [192.168.70.166] RRQ 34 bytes:
09-19-51-738| [192.168.70.166] 00000000: 38 39 30 65 66 37 62 65 2f 63 6f 6e 66 69 67 2e
09-19-51-738| [192.168.70.166] 00000010: 74 78 74 00 6f 63 74 65 74 00 74 73 69 7a 65 00
09-19-51-738| [192.168.70.166] 00000020: 30 00
09-19-51-738| [192.168.70.166] "890ef7be\config.txt": tsize is requested, blksize default.
09-19-51-738| [192.168.70.166] "config.txt": file not found in "C:\ProgramData\WTware\Terminals\B8.27.EB.0E.F7.BE\".
09-19-51-753| [192.168.70.166] "890ef7be\config.txt": "C:\Program Files (x86)\WTware\TFTPDROOT\5.8.46\pi2\localboot\config.txt".
09-19-51-753| [192.168.70.166] "890ef7be\config.txt": completed.
09-19-51-753| [192.168.70.166] RRQ 36 bytes:
09-19-51-753| [192.168.70.166] 00000000: 38 39 30 65 66 37 62 65 2f 72 65 63 6f 76 65 72
09-19-51-753| [192.168.70.166] 00000010: 79 2e 65 6c 66 00 6f 63 74 65 74 00 74 73 69 7a
09-19-51-753| [192.168.70.166] 00000020: 65 00 30 00
09-19-51-753| [192.168.70.166] "890ef7be\recovery.elf": tsize is requested, blksize default.
09-19-51-753| [192.168.70.166] "890ef7be\recovery.elf": file not found: "C:\Program Files (x86)\WTware\TFTPDROOT\890ef7be\recovery.elf".
09-19-51-769| [192.168.70.166] RRQ 33 bytes:
09-19-51-769| [192.168.70.166] 00000000: 38 39 30 65 66 37 62 65 2f 73 74 61 72 74 2e 65
09-19-51-769| [192.168.70.166] 00000010: 6c 66 00 6f 63 74 65 74 00 74 73 69 7a 65 00 30
09-19-51-769| [192.168.70.166] 00000020: 00
09-19-51-769| [192.168.70.166] "890ef7be\start.elf": tsize is requested, blksize default.
09-19-51-769| [192.168.70.166] "890ef7be\start.elf": "C:\Program Files (x86)\WTware\TFTPDROOT\5.8.46\pi2\localboot\start.elf".
09-19-53-816| [192.168.70.166] Timeout occured while transfer "890ef7be\start.elf".
09-19-53-816| [192.168.70.166] Resend block 361.
09-19-55-925| [192.168.70.166] Timeout occured while transfer "890ef7be\start.elf".
09-19-55-925| [192.168.70.166] Resend block 723.
09-19-57-943| [192.168.70.166] Timeout occured while transfer "890ef7be\start.elf".
09-19-57-943| [192.168.70.166] Resend block 802.
09-20-00-273| [192.168.70.166] Timeout occured while transfer "890ef7be\start.elf".
09-20-00-273| [192.168.70.166] Resend block 2108.
09-20-01-164| [192.168.70.166] "890ef7be\start.elf": completed.
09-20-01-164| [192.168.70.166] RRQ 33 bytes:
09-20-01-164| [192.168.70.166] 00000000: 38 39 30 65 66 37 62 65 2f 66 69 78 75 70 2e 64
09-20-01-164| [192.168.70.166] 00000010: 61 74 00 6f 63 74 65 74 00 74 73 69 7a 65 00 30
09-20-01-164| [192.168.70.166] 00000020: 00
09-20-01-179| [192.168.70.166] "890ef7be\fixup.dat": tsize is requested, blksize default.
09-20-01-179| [192.168.70.166] "890ef7be\fixup.dat": "C:\Program Files (x86)\WTware\TFTPDROOT\5.8.46\pi2\localboot\fixup.dat".
09-20-01-179| [192.168.70.166] "890ef7be\fixup.dat": completed.

akatik
SUPPORT
SUPPORT
Posts: 344
Joined: Mon Jan 17, 2005 6:30 pm
Contact:

Re: R-Pi Won't boot from SD Card using TFTP

Post by akatik » Sat Feb 09, 2019 2:27 pm

nnh775 wrote:
Fri Feb 08, 2019 8:28 pm
I upgraded from 5.8.26 to the latest 5.8.46, and my raspberry's
Which raspberry model do you use?
nnh775 wrote:
Fri Feb 08, 2019 8:28 pm
The log says file not found:
Several files not found at every boot. It is OK.
nnh775 wrote:
Fri Feb 08, 2019 8:28 pm
09-19-53-816| [192.168.70.166] Timeout occured while transfer "890ef7be\start.elf".
09-19-53-816| [192.168.70.166] Resend block 361.
09-19-55-925| [192.168.70.166] Timeout occured while transfer "890ef7be\start.elf".
09-19-55-925| [192.168.70.166] Resend block 723.
09-19-57-943| [192.168.70.166] Timeout occured while transfer "890ef7be\start.elf".
09-19-57-943| [192.168.70.166] Resend block 802.
09-20-00-273| [192.168.70.166] Timeout occured while transfer "890ef7be\start.elf".
09-20-00-273| [192.168.70.166] Resend block 2108.
09-20-01-164| [192.168.70.166] "890ef7be\start.elf": completed.
Timeout/resend mean your network is not OK. Does it happen on every boot?

Remove everyting from USB ports and try to boot again. If it does not help, try local SD boot.

nnh775
Posts: 2
Joined: Fri Feb 08, 2019 8:05 pm

Re: R-Pi Won't boot from SD Card using TFTP

Post by nnh775 » Sun Feb 10, 2019 4:50 am

We had a deeper problem on our network. One of the fiber transceivers in my fiber switch started to fail, creating a broadcast storm. Finally got it fixed and wtware magically started working again, along with every other service on the network. Thank you for the reply through.

Post Reply