#Do i need to create boot partition serial

# /usr/local/DigiEL-5.2/usr/bin/mkimage -A arm -O linux -T script -C none -a 200000 -e 200000 -n cc9p9215js-bootscript -d cc9p9215-custom-commands.txt cc9p9215js-bootscript Save this as: cc9p9215-custom-commands.txt Compile this into a bootscript image file with the command: Intnvram set partition add name=RootFS start=190000 size=180000 type=Filesystem flag_fs_type=SQUASHFS flag_fs_root=yes Intnvram set partition add name=RootFS start=200000 size=E00000 type=Filesystem flag_fs_type=JFFS2 flag_fs_root=yes Intnvram set partition add name=Kernel start=50000 size=140000 type=Linux-Kernel

Intnvram set partition add name=Kernel start=80000 size=180000 type=Linux-Kernel

if you configured a module interactively with 'flpart' reset linux quit and save, you can check the addresses to pass to the intnvram with intnvram printall.Д¬reate a txt file with an empty last row ending with 0x0a 0x0aВ (no DOS CR/LF in it): Drawback: the bootscript is then very dependent on the module and the size of flash and partitions.ДЇirst of all determine which partition start address and size you need. The workaround is to update the uboot with non-interactive commands and to create the needed Linux partitions with 'intnvram' also in non-interactive mode.

#Do i need to create boot partition serial

However when using this for production, it does not allow to run 'flpart' or 'update uboot' from this, as those commands are interactively using the serial port. U-Boot autoscript feature is described in /usr/local/DigiEL-5.2/docs/Software/U-Boot_Reference_Manual.pdf Revision H in section 6.