home.md

@@ -50,10 +50,43 @@ make
 ### The easy way - pre-packaged binaries:
 
 The easiest way is to use the binaries we already packaged:
-* S905D2 - U200 : [fip-collect-g12a-g12a_u200_v1-20190110-184413.tar.xz](uploads/aaa5fa102c30bb3b0ec2d3dd1a563eca/fip-collect-g12a-g12a_u200_v1-20190110-184413.tar.xz)
-* S905X2 - U211 : [fip-collect-g12a-g12a_u211_v1-20190213-092553.tar.xz](uploads/818ebd4ee7d91a588aa197a5ccd9e03e/fip-collect-g12a-g12a_u211_v1-20190213-092553.tar.xz)
+* S905D2 - U200 : [fip-collect-g12a-g12a_u200_v1-amlogic-dev_9.2.1811_21-20190912-112355.tar.xz](uploads/294a0db16739f03ea871df1e69bdc690/fip-collect-g12a-g12a_u200_v1-amlogic-dev_9.2.1811_21-20190912-112355.tar.xz)
+* S905X2 - U211 : [fip-collect-g12a-g12a_u211_v1-amlogic-dev_9.2.1811_21-20190912-112612.tar.xz](uploads/1da4155bd4932c37deb474b0c9b2a765/fip-collect-g12a-g12a_u211_v1-amlogic-dev_9.2.1811_21-20190912-112612.tar.xz)
+* S905X3 - AC200 : [fip-collect-g12a-sm1_ac200_v1-amlogic-dev_9.2.1811_21-20190912-113043.tar.xz](uploads/12e2d6d5b5569fb45e40e034321bdad0/fip-collect-g12a-sm1_ac200_v1-amlogic-dev_9.2.1811_21-20190912-113043.tar.xz)
 
-### The hard way - packaging the binaries from Amlogic's buildroot:
+### The hard way - packaging the binaries from Amlogic's GIT repositories:
+
+The goal here is to collect the bl2, bl21, bl30, bl31, bl301 and acs.bin
+Some of these binaries are directly provided by the buildroot package of Amlogic, other must be generated from the vendor u-boot.
+
+Use this script [collect-aml-binaries-git-refboard.sh](uploads/0bc0db53b2f507d87ffa4e00ce26c833/collect-aml-binaries-git-refboard.sh) which will do it for you
+```
+./collect-aml-binaries-git-refboard.sh <openlinux branch> <soc> <refboard>
+```
+For SM1/AC200:
+```
+./collect-aml-binaries-git-refboard.sh amlogic-dev_9.2.1811_21 sm1 sm1_ac200_v1
+```
+
+## Package the Binaries
+
+To package the binaries together and make something we can flash, we must follow some obscure procedure which you can read in the scripts that amlogic's buildroot uses.
+These tends to change betweeen soc and u-boot versions. Best is to just use what we previously packaged and this script [generate-bins-new.sh](uploads/2103b12fe2d91bdb543447783e20ef53/generate-bins-new.sh)
+
+```shell
+./generate-bins-new.sh <fip-collect-directory> <target-bl33-binary>
+```
+this will generate a directory with the following binaries
+* `u-boot.bin`: binary to flash on the emmc or the spi:
+  * emmc: remember skip the first sector: 
+```shell
+mmc dev 1 1
+mmc write $fileaddr 1 $bin_block_num 
+```
+You may choose to write the u-boot on the boot partitions of the eMMC. The boot order is `user` -> `boot 0` -> `boot 1`.
+* `u-boot.bin.sd.bin` : **NO YET TESTED** Binary to boot from an sdcard: remember to leave room for the MBR : [write-u-boot.sh](uploads/0b4d640b26473a2783751482d1e311e8/write-u-boot.sh)
+
+### DEPRECATED The hard way - packaging the binaries from Amlogic's buildroot:
 
 The goal here is to collect the bl2, bl21, bl30, bl31, bl301 and acs.bin
 Some of these binaries are directly provided by the buildroot package of Amlogic, other must be generated from the vendor u-boot.
@@ -86,7 +119,7 @@ OR you can use this script [collect-aml-binaries-new.sh](uploads/afa7f471af14fad
 ./collect-aml-binaries-new.sh <buildroot dir> g12a g12a_u200_v1
 ```
 
-## Package the Binaries
+## DEPRECATED Package the Binaries
 
 To package the binaries together and make something we can flash, we must follow some obscure procedure which you can read in the scripts that amlogic's buildroot uses.
 These tends to change betweeen soc and u-boot versions. Best is to just use what we previously packaged and this script [generate-bins-new.sh](uploads/425dd3fd9b999bbc08c3c3b5e95664e7/generate-bins-new.sh)