User Tools

Site Tools



en:uboot

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
en:uboot [2024/04/07 11:12] – [tftp] franken:uboot [2024/04/07 13:07] (current) – [U-Boot] frank
Line 4: Line 4:
 it needs a bit of time to add all into this page... it needs a bit of time to add all into this page...
  
 +My U-Boot source (with prebuilt binaries in releases):
 +
 +https://github.com/frank-w/u-boot/
 ===== board specific pages ===== ===== board specific pages =====
  
Line 13: Line 16:
   * [[.:bpi-r4:uboot|BPI-R4]]   * [[.:bpi-r4:uboot|BPI-R4]]
  
-===== load files =====+my u-boot have builtin environment created by the uEnv_r*.txt which can be overridden by an uEnv.txt file when kernel-files (r2/r64: bananapi/bpi-r*/linux, all others in root) are located on mmc BPI-BOOT partition. 
 +===== load/write data =====
  
 +listing files (mmc=subsystem, 0=device, 5=partition, folder optional):
 +
 +  ls mmc 0:5 folder
 +
 +basicly load works from fat partitions with the following syntax (ext4 should work too, but with [[https://github.com/u-boot/u-boot/blob/master/doc/README.ext4|ext4load]])...
 +
 +loading files (mmc=subsystem, 0=device, 5=partition):
 +
 +  fatload mmc 0:5 $loadaddr filename
 +
 +most complete page for writing to a device (including nand/nor) is [[.:bpi-r3:uboot|BPI-R3]]
 ==== mmc ==== ==== mmc ====
  
  
-all BPI-Router boards+all BPI-Router boards (R3+R4 have only 1 mmc controller so it is based on hardware switches which is available)
  
 <code> <code>
Line 49: Line 64:
 ls mmc 0:1 ls mmc 0:1
 </code> </code>
 +
 +loading files (0=device, 5=partition):
 +
 +  fatload mmc 0:5 $loadaddr filename
  
 === eMMC === === eMMC ===
Line 105: Line 124:
 </code> </code>
  
 +loading files:
 +
 +  fatload usb 0:1 $loadaddr filename
 ==== sata ==== ==== sata ====
  
Line 146: Line 168:
 drivers/pci/pcie_mediatek_gen3.c:mtk_pcie_startup_port[261] detected a card drivers/pci/pcie_mediatek_gen3.c:mtk_pcie_startup_port[261] detected a card
 set trans table 0: 0x20000000 0x20000000, 0x10000000 set trans table 0: 0x20000000 0x20000000, 0x10000000
-BPI-R3M> clk dump 
- Rate               Usecnt      Name 
------------------------------------------- 
- 12000000                    |-- dummy12m 
 BPI-R3M> nvme scan BPI-R3M> nvme scan
 BPI-R3M> nvme info                                                               BPI-R3M> nvme info                                                              
Line 159: Line 177:
  
 ==== tftp ==== ==== tftp ====
 +
 +network support is basicly on all boards possible with my uboot
 +
 +  * r2pro only wan-port (mtk switch driver not compatible with rockchip mac driver in uboot, but wan is directly connected to RJ45 jack)
 +  * r3mini only lan-port (only 1 phy can be defined)
 +  * R3/R4 only RJ45 ethernet ports (no SFP)
  
 [[.:bpi-r2:netboot]] [[.:bpi-r2:netboot]]
Line 170: Line 194:
  
 IP-adress of server (including the : ) can be omitted, if serverip is set correctly IP-adress of server (including the : ) can be omitted, if serverip is set correctly
-===== boot files =====+===== booting ===== 
 + 
 +if the file is at $loadaddr you use it 
 + 
 +==== uboot.bin ==== 
 + 
 +  go $loadaddr 
 + 
 +==== Kernel-Image ==== 
 + 
 +BPI-R2 (armhf) uses uImage with appended devicetree, all other boards are using FIT image 
 + 
 +all can be booted with bootm, FIT have bootconfig where 1 can be set as default, so this is optional 
 + 
 + 
 +  bootm $loadaddr#config 
 + 
 +available configs in a FIT can be obtained on host-linux with uboot-tools installed (or look in its file when kernel is self-compiled)
  
 +  dumpimage -l bpi-r3.itb
en/uboot.1712481160.txt.gz · Last modified: 2024/04/07 11:12 by frank