Changes between Version 22 and Version 23 of venice/firmware
- Timestamp:
- 05/06/2025 04:17:36 PM (7 weeks ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
venice/firmware
v22 v23 99 99 100 100 If updating via U-Boot you will need to setup a TFTP server to host the files for transfer or alternatively you could load firmware files from removable storage (microSD, or USB Mass Storage for example). For details on setting up a TFTP server see [wiki:tftpserver here]. Also note that there are many reasons why TFTP may fail including: 101 * firewall issue keeping your TFTP server for being accessible (make sure you can ping it!)102 * invalid network configuration (netmask, gatewayip, ipaddr, serverip) - again make sure you can ping it!101 * Firewall issue keeping your TFTP server for being accessible (make sure you can ping it!) 102 * Invalid network configuration (netmask, gatewayip, ipaddr, serverip) - again make sure you can ping it! 103 103 * 'TFTP error: trying to overwrite reserved memory...' - indicates you are trying to transfer a file that is larger than system memory. You will need to split the file into chunks and flash them individually at the right offsets 104 104 … … 111 111 112 112 ==== Compressed disk image via U-Boot 113 A Compressed disk image (Ubuntu, OpenWrt, etc) in the .img.gz file format can be installed from U-Boot as long as you can load it into memory (ie via ethernet/TFTP or removable storage): 113 A Compressed disk image (Ubuntu, OpenWrt, etc) in the .img.gz file format can be installed from U-Boot as long as you can load it into memory (ie via ethernet/TFTP or removable storage): 114 * First, setup the TFTP server with these instructions [wiki:tftpserver] and place the file on the server 114 115 * Using ethernet and a TFTP server using the 'update_all' script: 115 116 {{{#!bash