Changes between Version 14 and Version 15 of newport/bootloader


Ignore:
Timestamp:
04/25/2019 06:49:41 PM (5 months ago)
Author:
Tim Harvey
Comment:

updated for kernel.itb and newport.scr bootscript being moved to root partition /boot directory

Legend:

Unmodified
Added
Removed
Modified
  • newport/bootloader

    v14 v15  
    163163Additionally you should note the following:
    164164 - use load/ls/save commands which support FAT/ext filesystem types automatically instead of the fs specific commands
    165  - if using a root filesystem that is not supported by the bootloader (ie F2FS or BTRFS) you can place your kernel image in the FAT12 filesystem on partition 1 of the boot device. This filesystem is part of the 16MB 'Boot Firmware' image. If doing so you will need to compress the kernel and package it into a [#fit FIT image] in order to fit it in the available space.
     165 - if using a root filesystem that is not supported by the bootloader (ie F2FS or BTRFS) you can place your bootscript and kernel image in the FAT12 filesystem on partition 1 of the boot device. This filesystem is part of the 16MB 'Boot Firmware' image. If doing so you will need to compress the kernel and package it into a [#fit FIT image] in order to fit it in the available space.
    166166
    167167The Distro-Config environment supports legacy uImage scripts (it does not support FIT images with scripts). You can create these with the {{{mkimage}}} tool from U-Boot as such:
     
    170170}}}
    171171
    172 You can then place the uImage {{{newport.scr}}} on a bootable partition such as the embedded FAT12 filesystem within the Newport boot firmware as such:
     172The bootscript can be updated at runtime on the target. For example:
     173{{{#!bash
     174mkimage -A arm64 -T script -C none -d ubuntu.txt /boot/newport.scr
     175}}}
     176
     177If storing the bootscript on the embedded FATFS partition (which would make sense if your root filesystem is something that is not supported by the Bootloader such as F2FS or BTRFS):
     178 * You can update the bootscript uImage {{{newport.scr}}} in the boot firmware:
    173179{{{#!bash
    174180fatfs-tool -i firmware-newport.img cp newport.scr /
    175181}}}
    176 
    177 Alternatively this can be done at runtime on the target within Linux by mounting the FAT12 partition. For example:
     182 * You can udpate the bootscript uImage {{{newport.scr}}} on a live target via:
    178183{{{#!bash
    179184mount /dev/mmcblk0p1 /mnt
     
    181186umount
    182187}}}
     188
    183189
    184190