|
| 1 | +After that in the directory "/home/promwad/microchip_buildroot/buildroot-external-microchip/board/microchip/polarberry" you can find script for board flashing. |
| 2 | + |
| 3 | +There are 4 scipts: |
| 4 | +1) Program_HSS_to_eNVM.sh |
| 5 | +2) Program_UBOOT_to_eMMC.sh |
| 6 | +3) Program_LINUX_to_eNVM.sh |
| 7 | +4) Program_ALL_to_Polarberry.sh |
| 8 | + |
| 9 | +and settings file: FLASH_CONFIG.CONF |
| 10 | + |
| 11 | +Script is used to burn images to the Polarberry board. |
| 12 | + |
| 13 | +The 1th is used to program ONLY HSS bootloader umage to the Polarberry board. |
| 14 | +The 2th is used to program ONLY UBOOT image to the Polarberry board. |
| 15 | +The 3th is used to program ONLY LINUX (Kernel and root filesystem, bith) image to the Polarberry board. |
| 16 | +The 4th is used to program ALL (HSS, UBOOT, LINUX) images to the Polarberry oard. |
| 17 | + |
| 18 | + |
| 19 | +The 1th script can be used with virgin Polarberry boards and requires ONLY JTAG connection with the board. |
| 20 | +The 2th script can be used only after 1th was used (it means UBOOT programming requires HSS was installed before) |
| 21 | + and requires JTAG and UART connection with the board. |
| 22 | +The 3th script can be used only after 2th was used (it means Linux programming requires UBOOT (as HSS toot) |
| 23 | + was installed before) and requires JTAG, UART and ETHERNET connection with the board. |
| 24 | +The 4th script runs 1,2,3 one-by-one and do all thunigs that do 1,2,3 in automatic mode and requires JTAG |
| 25 | + UART and ETHERNET connection with the board. Can be used with virgin Polarberry boards too. |
| 26 | + |
| 27 | +Before script can be used, you need to fix values in FLASH_CONFIG.CONF according to your PC. |
| 28 | +The file contains strings with comments, so you can advice what you need: |
| 29 | + |
| 30 | +BUILDROOT_DIRECTORY - here you need to set PATH to the buildroot you are using |
| 31 | +UART_DEVICE - here you need to set the name of the UART in your system. (/dev/ttyUSB1 for example) |
| 32 | +DEVICE_IP - here you need to set IP ADDRESS that will be set on the board during flashing. |
| 33 | + It shall be one of the free/unused IP addresses from you network. |
| 34 | + |
| 35 | +PC_IP - here you need to set IP ADDRESS of the PC you are using. (It can be obtained via "ifconfig" command) |
| 36 | +IMAGE_NAME - here you need to set file name with LINUX image that is placed on the TFTP server |
| 37 | + (default value is "fitimage_polarberry.itb", and this file is built by buildroot and placed in "output/images" directory) |
| 38 | + |
| 39 | + |
| 40 | +To start building images via buildroot you need to run this command in buildrood sources: |
| 41 | +1) "make sundancedsp_polarberry_defconfig BR2_EXTERNAL=../buildroot-external-microchip" |
| 42 | + (where BR2_EXTERNAL shall point to the mbuildroot microsemi sources). |
| 43 | + |
| 44 | +2) "make" |
| 45 | + Building will take time. Succesfull building will finish like this: |
| 46 | + |
| 47 | +FIT description: Linux fitImage for Polaberry |
| 48 | +Created: Wed Nov 22 05:06:16 2023 |
| 49 | + Image 0 (kernel-0) |
| 50 | + Description: Linux Kernel |
| 51 | + Created: Wed Nov 22 05:06:16 2023 |
| 52 | + Type: Kernel Image |
| 53 | + Compression: uncompressed |
| 54 | + Data Size: 17612800 Bytes = 17200.00 KiB = 16.80 MiB |
| 55 | + Architecture: RISC-V |
| 56 | + OS: Linux |
| 57 | + Load Address: 0x80200000 |
| 58 | + Entry Point: 0x80200000 |
| 59 | + Hash algo: sha256 |
| 60 | + Hash value: 466f36e4c778103ce7ef2fa9dc3456cb1e25d291fe71ab96f3d88ac588004f11 |
| 61 | + Image 1 (fdt-0) |
| 62 | + Description: Flattened Device Tree blob |
| 63 | + Created: Wed Nov 22 05:06:16 2023 |
| 64 | + Type: Flat Device Tree |
| 65 | + Compression: uncompressed |
| 66 | + Data Size: 14949 Bytes = 14.60 KiB = 0.01 MiB |
| 67 | + Architecture: RISC-V |
| 68 | + Hash algo: sha256 |
| 69 | + Hash value: 1ccea6c67588f89a9227a5018b98048390728ef3a21ba90cbd69d8ab750843a4 |
| 70 | + Image 2 (ramdisk-0) |
| 71 | + Description: ramdisk |
| 72 | + Created: Wed Nov 22 05:06:16 2023 |
| 73 | + Type: RAMDisk Image |
| 74 | + Compression: uncompressed |
| 75 | + Data Size: 4921601 Bytes = 4806.25 KiB = 4.69 MiB |
| 76 | + Architecture: AArch64 |
| 77 | + OS: Linux |
| 78 | + Load Address: unavailable |
| 79 | + Entry Point: unavailable |
| 80 | + Hash algo: sha256 |
| 81 | + Hash value: cae144f8a5c8eb441ba01aae3d3dc1c88ea0303afe710e7d7528d04b0e963997 |
| 82 | + Default Configuration: 'conf-1' |
| 83 | + Configuration 0 (conf-1) |
| 84 | + Description: Boot Linux kernel with FDT blob + ramdisk |
| 85 | + Kernel: kernel-0 |
| 86 | + Init Ramdisk: ramdisk-0 |
| 87 | + FDT: fdt-0 |
| 88 | + Hash algo: sha256 |
| 89 | + Hash value: unavailable |
| 90 | + Configuration 1 (conf-2) |
| 91 | + Description: Boot Linux kernel with FDT blob |
| 92 | + Kernel: kernel-0 |
| 93 | + FDT: fdt-0 |
| 94 | + Hash algo: sha256 |
| 95 | + Hash value: unavailable |
| 96 | + |
| 97 | + |
| 98 | +To flash the images to the Polarberry board: |
| 99 | +1) Fix FLASH_CONFIG.CONF file in the board/microchip/polarberry directory. |
| 100 | +2) Power ON the Polarberry board |
| 101 | +3) run "Program_ALL_to_Polarberry.sh", and wait until all finished. |
0 commit comments