failed boot via tftp
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2019-09-08 11:54 PM
I tried booting via TFTP boot and got the following reply
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
DHCP client bound to address 192.168.1.2 (766 ms)
missing environment variable: pxeuuid
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/01-00-80-e1-42-56-51
Using ethernet@5800a000 device
TFTP from server 192.168.1.94; our IP address is 192.168.1.2
Filename 'pxelinux.cfg/01-00-80-e1-42-56-51'.
Load address: 0xc4200000
Loading: #
0 Bytes/s
done
Bytes transferred = 248 (f8 hex)
Config file found
Select the boot mode
1: Linux 4.19.9
Enter choice: 1: Linux 4.19.9
missing environment variable: bootfile
Retrieving file: uImage
Using ethernet@5800a000 device
TFTP from server 192.168.1.94; our IP address is 192.168.1.2
'.lename 'uImage
Load address: 0xc2000000
Loading: *
TFTP error: 'File not found' (1)
Not retrying...
for failure retrieving kernel
this is my /tftpboot tree
.
├── pxelinux.cfg
│ ├── 01-00-80-e1-42-56-51 -> default-arm-stm32mp
│ └── default-arm-stm32mp
├── stm32mp157c-dk2.dtb
└── uImage
I tested the TFTP server is available, all files are available for download.
Where is the problem?
Solved! Go to Solution.
- Labels:
-
STM32MP15 Lines
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2019-09-09 6:09 PM
The reason is default-arm-stm32mp file use CRLF not LF,now it work
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2019-09-09 1:04 AM
Hi @Jzhua
Can you please confirm you have followed this guideline
https://wiki.st.com/stm32mpu/wiki/How_to_boot_the_kernel_via_TFTP_from_U-Boot
Thx
Olivier
In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2019-09-09 1:32 AM
yes,I was followed this guideline
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2019-09-09 7:57 AM
Hi @Jzhua
I succeed to boot on tftp with the procedure.
content of my tftpboot directory ( I used artifact from defaut st-image-weston stm32mp1-disco image)
/tftboot :
drwxrwxr-x 2 osboxes osboxes 4096 Sep 9 12:44 pxelinux.cfg
-rwxrwxrwx 1 osboxes osboxes 69510 Sep 9 10:31 stm32mp157c-dk2--4.19-r0-stm32mp1-disco-20190909122915.dtb
lrwxrwxrwx 1 osboxes osboxes 68 Sep 9 12:31 stm32mp157c-dk2.dtb -> /tftpboot/stm32mp157c-dk2--4.19-r0-stm32mp1-disco-20190909122915.dtb
lrwxrwxrwx 1 osboxes osboxes 59 Sep 9 12:30 uImage -> /tftpboot/uImage--4.19-r0-stm32mp1-disco-20190909122915.bin
-rwxrw-rw- 1 osboxes osboxes 6555552 Sep 9 10:29 uImage--4.19-r0-stm32mp1-disco-20190909122915.bin
Content of pxelinux.cfg/01-00-80-e1-42-4c-e8
menu title Select the boot mode
DEFAULT ramfs
LABEL ramfs
KERNEL uImage
FDT stm32mp157c-dk2.dtb
APPEND rootwait rw earlyprintk console=ttyS3,115200
I need to remove line 'INITRD uInitrd' in order it works.
Problem looks to come from this broken line in your trace :
TFTP from server 192.168.1.94; our IP address is 192.168.1.2
'.lename 'uImage
On my side I got :
TFTP from server 10.xx.***.49; our IP address is 10.xx.***.120
Filename 'uImage'.
Check for any syntax issue ?
Hope it help
Olivier
In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2019-09-09 6:09 PM
The reason is default-arm-stm32mp file use CRLF not LF,now it work
