```
### 2.5 Generate fip/nexell compatable image
-The u-boot.bin (or u-boot-dtb.bin) cannot be loaded by bl1/bl2 bootloaders. You have to generate
+The u-boot-dtb.bin cannot be loaded by bl1/bl2 bootloaders. You have to generate
a fip image and boot image for nexell bl1.
#### ARTIK710
-- generate a fip-nonsecure.bin image using fip_create tool(input: u-boot.bin or u-boot-dtb.bin, output:fip-nonsecure.bin)
-- Please prefer to use u-boot-dtb.bin over u-boot.bin if it exists. It depends on the version of U-BOOT you are using.
+- generate a fip-nonsecure.bin image using fip_create tool(input: u-boot-dtb.bin, output:fip-nonsecure.bin)
```
-[ -e u-boot-dtb.bin ] && UBOOT=u-boot-dtb.bin || UBOOT=u-boot.bin
tools/fip_create/fip_create \
- --dump --bl33 $UBOOT \
+ --dump --bl33 u-boot-dtb.bin \
fip-nonsecure.bin
```
- generate a fip-nonsecure.img using SECURE_BINGEN tool(input: fip-nonsecure.bin, output: fip-nonsecure.img)
#### ARTIK530
- generate a bootloader.img using BOOT_BINGEN tool
-- Please prefer to use u-boot-dtb.bin if it exists.
```
-[ -e u-boot-dtb.bin ] && UBOOT=u-boot-dtb.bin || UBOOT=u-boot.bin
tools/nexell/SECURE_BINGEN \
-c S5P4418 -t 3rdboot \
-n tools/nexell/nsih/raptor-sd.txt \
- -i $UBOOT \
+ -i u-boot-dtb.bin \
-o bootloader.img \
-l 0x94c00000 -e 0x94c00000
```