Skip to content

Commit eb0043f

Browse files
andrum99JamesH65
authored andcommitted
bootmodes/net.md: fix error in Markdown affecting multi-level list (raspberrypi#1273)
1 parent 387bc79 commit eb0043f

File tree

1 file changed

+4
-4
lines changed
  • hardware/raspberrypi/bootmodes

1 file changed

+4
-4
lines changed

hardware/raspberrypi/bootmodes/net.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -13,11 +13,11 @@ To network boot, the boot ROM does the following:
1313
* ARP to tftpboot server
1414
* ARP reply includes tftpboot server ethernet address
1515
* TFTP RRQ 'bootcode.bin'
16-
* File not found: Server replies with TFTP error response with textual error message
17-
* File exists: Server will reply with the first block (512 bytes) of data for the file with a block number in the header
18-
* Pi replies with TFTP ACK packet containing the block number, and repeats until the last block which is not 512 bytes
16+
* File not found: Server replies with TFTP error response with textual error message
17+
* File exists: Server will reply with the first block (512 bytes) of data for the file with a block number in the header
18+
* Pi replies with TFTP ACK packet containing the block number, and repeats until the last block which is not 512 bytes
1919
* TFTP RRQ 'bootsig.bin'
20-
* This will normally result in an error `file not found`. This is to be expected, and TFTP boot servers should be able to handle it.
20+
* This will normally result in an error `file not found`. This is to be expected, and TFTP boot servers should be able to handle it.
2121

2222
From this point the `bootcode.bin` code continues to load the system. The first file it will try to access is [`serial_number`]/start.elf. If this does not result in a error then any other files to be read will be pre-pended with the `serial_number`. This is useful because it enables you to create separate directories with separate start.elf / kernels for your Pis
2323
To get the serial number for the device you can either try this boot mode and see what file is accessed using tcpdump / wireshark, or you can run a standard Raspbian SD card and `cat /proc/cpuinfo`.

0 commit comments

Comments
 (0)