Content Comparison

...

The sources are pulled from:

1. arm-trusted firmware: GitHub - ARM-software/arm-trusted-firmware

2. mv-ddr-marvell: GitHub - MarvellEmbeddedProcessors/mv-ddr-marvell

3. u-boot: currently from marvell SDK

4. linux: GitHub - torvalds/linux: Linux kernel source tree

5. patches are supplied by Solid-Run in the patches/ directory

6. binaries are supplied by Solid-Run in the binaries/ directory
   

   The build script builds the u-boot, atf and linux components, integrate it with Ubuntu rootfs bootstrapped with multistrap. Buildroot is also built aside for future use.

U-Boot based on SDK10 

The CN913x u-boot is not public yet, and was taken from Marvell's SDK10

...

The board can be configured based on the amount of CP# devices and to which carrier board it will fit. There are a few parameters that must be taken to account:

1. CP_NUM:
   

   1. CP_NUM=1 - CN9130

   2. CP_NUM=2 - CN9131

   3. CP_NUM=3 - CN9132

2. BOARD_CONFIG - defines the device tree based on the platform
   

   1. BOARD_CONFIG=0 - CN9132 CEx7 based on Clearfog Eval Board

   2. BOARD_CONFIG=1 - CN9130 SOM based on Clearfog Base

   3. BOARD_CONFIG=2 - CN9130 SOM based on Clearfog Pro

   4. BOARD_CONFIG=3 - CN9131 based on SolidWan

Note: when defining the BOARD_CONFIG, the runme.sh script defines correct CP_NUM related to the platform.

...

The script will generate a ready to use images at ROOTDIR/images:

1. flash_image.bin for SPI

2. *.img for eMMC or SD card

Boot Select

Before powering up the board  for the first time it is recommended to select the boot media. In order to configure the boot media:

...

...