[U-Boot] [PATCH] rockchip: doc: update latest info to document

[U-Boot] [PATCH] rockchip: doc: update latest info to document

[Kever Yang]

- Add some rk3399 and rk3328 boards;
- use rkdeveloptool instead of rkflashtool;
- use opensource.rock-chips.com instead of wikidot;
- other update.

Signed-off-by: Kever Yang <kever.yang@rock-chips.com>
---

 doc/README.rockchip | 38 ++++++++++++++++++++++++--------------
 1 file changed, 24 insertions(+), 14 deletions(-)

diff --git a/doc/README.rockchip b/doc/README.rockchip
index 2d8cf9f..229db0d 100644
--- a/doc/README.rockchip
+++ b/doc/README.rockchip
@@ -14,9 +14,6 @@ many Rockchip devices [1] [2].
 The current mainline support is experimental only and is not useful for
 anything. It should provide a base on which to build.
 
-So far only support for the RK3288 and RK3036 is provided.
-
-
 Prerequisites
 =============
 
@@ -26,17 +23,18 @@ You will need:
    - Power connection to 5V using the supplied micro-USB power cable
    - Separate USB serial cable attached to your computer and the Firefly
         (connect to the micro-USB connector below the logo)
-   - rkflashtool [3]
-   - openssl (sudo apt-get install openssl)
+   - rkdeveloptool [3]
    - Serial UART connection [4]
+   - loader file[5].
    - Suitable ARM cross compiler, e.g.:
         sudo apt-get install gcc-4.7-arm-linux-gnueabi
 
+Reference to Rockchip document for more detail about boot option[6].
 
 Building
 ========
 
-At present eight RK3288 boards are supported:
+Eight RK3288 boards are supported:
 
    - EVB RK3288 - use evb-rk3288 configuration
    - Fennec RK3288 - use fennec-rk3288 configuration
@@ -47,11 +45,20 @@ At present eight RK3288 boards are supported:
    - Radxa Rock 2 - use rock2 configuration
    - Tinker RK3288 - use tinker-rk3288 configuration
 
-Two RK3036 board are supported:
+Two RK3036 boards are supported:
 
    - EVB RK3036 - use evb-rk3036 configuration
    - Kylin - use kylin_rk3036 configuration
 
+RK3399 boards supported:
+   - EVB RK3399 - use evb-rk3036 configuration
+   - Firefly RK3399 - use firefly-rk3399 configuration
+   - RK3399-Q7 - use puma-rk3399 configuration
+
+RK3328 boards supported
+   - EVB RK3328 - use evb-rk3328 configuration
+
+
 For example:
 
    CROSS_COMPILE=arm-linux-gnueabi- make O=firefly firefly-rk3288_defconfig all
@@ -64,6 +71,7 @@ Writing to the board with USB
 
 For USB to work you must get your board into ROM boot mode, either by erasing
 your MMC or (perhaps) holding the recovery button when you boot the board.
+
 To erase your MMC, you can boot into Linux and type (as root)
 
    dd if=/dev/zero of=/dev/mmcblk0 bs=1M
@@ -72,9 +80,10 @@ Connect your board's OTG port to your computer.
 
 To create a suitable image and write it to the board:
 
-   ./firefly-rk3288/tools/mkimage -n rk3288 -T rkimage -d \
-	./firefly-rk3288/spl/u-boot-spl-dtb.bin out && \
-   cat out | openssl rc4 -K 7c4e0304550509072d2c7b38170d1711 | rkflashtool l
+   ./firefly-rk3288/tools/mkimage -n rk3288 -T rksd -d \
+	./firefly-rk3288/spl/u-boot-spl-dtb.bin idbspl.img && \
+	rkdeveloptool db rkbin/rk32/rk3288_loader_v1.01.232.bin \
+	rkdeveloptool wl 64 idbspl.img
 
 If all goes well you should something like:
 
@@ -243,7 +252,6 @@ Future work
 
 Immediate priorities are:
 
-- USB host
 - USB device
 - Run CPU at full speed (code exists but we only see ~60 DMIPS maximum)
 - NAND flash
@@ -257,9 +265,11 @@ Development Notes
 There are plenty of patches in the links below to help with this work.
 
 [1] https://github.com/rkchrome/uboot.git
-[2] https://github.com/linux-rockchip/u-boot-rockchip.git branch u-boot-rk3288
-[3] https://github.com/linux-rockchip/rkflashtool.git
+[2] https://github.com/rockchip-linux/u-boot.git branch release
+[3] https://github.com/rockchip-linux/rkdeveloptool.git
 [4] http://wiki.t-firefly.com/index.php/Firefly-RK3288/Serial_debug/en
+[5] https://github.com/rockchip-linux/rkbin.git
+[6] http://opensource.rock-chips.com/wiki_Boot_option
 
 rkimage
 -------
@@ -330,7 +340,7 @@ With this GPT partition layout, uboot can be compatilbe with other components,
 like miniloader, trusted-os, arm-trust-firmware.
 
 There are some documents about partitions in the links below.
-http://rockchip.wikidot.com/partitions
+http://opensource.rock-chips.com/wiki_Partitions
 
 --
 Simon Glass <sjg@chromium.org>
-- 
1.9.1

[U-Boot] [PATCH] rockchip: doc: update latest info to document

[Heiko Stübner]

Hi Kever,

Am Montag, 15. Mai 2017, 21:18:00 CEST schrieb Kever Yang:
> - Add some rk3399 and rk3328 boards;
> - use rkdeveloptool instead of rkflashtool;
> - use opensource.rock-chips.com instead of wikidot;
> - other update.
> 
> Signed-off-by: Kever Yang <kever.yang@rock-chips.com>
> ---
> 
>  doc/README.rockchip | 38 ++++++++++++++++++++++++--------------
>  1 file changed, 24 insertions(+), 14 deletions(-)
> 
> diff --git a/doc/README.rockchip b/doc/README.rockchip
> index 2d8cf9f..229db0d 100644
> --- a/doc/README.rockchip
> +++ b/doc/README.rockchip
> @@ -14,9 +14,6 @@ many Rockchip devices [1] [2].
>  The current mainline support is experimental only and is not useful for
>  anything. It should provide a base on which to build.
> 
> -So far only support for the RK3288 and RK3036 is provided.
> -
> -
>  Prerequisites
>  =============
> 
> @@ -26,17 +23,18 @@ You will need:
>     - Power connection to 5V using the supplied micro-USB power cable
>     - Separate USB serial cable attached to your computer and the Firefly
>          (connect to the micro-USB connector below the logo)
> -   - rkflashtool [3]
> -   - openssl (sudo apt-get install openssl)
> +   - rkdeveloptool [3]

In my personal opinion, rkflashtool should stay. You can very well add
rkdeveloptool as a second option, but rkflashtool was there first and
also is the one that most distributions contain in their repositories.
And both tools seem to have the same functionality.


Heiko

[U-Boot] [PATCH] rockchip: doc: update latest info to document

[Kever Yang]

On 05/16/2017 02:51 AM, Heiko Stübner wrote:
> Hi Kever,
>
> Am Montag, 15. Mai 2017, 21:18:00 CEST schrieb Kever Yang:
>> - Add some rk3399 and rk3328 boards;
>> - use rkdeveloptool instead of rkflashtool;
>> - use opensource.rock-chips.com instead of wikidot;
>> - other update.
>>
>> Signed-off-by: Kever Yang <kever.yang@rock-chips.com>
>> ---
>>
>>   doc/README.rockchip | 38 ++++++++++++++++++++++++--------------
>>   1 file changed, 24 insertions(+), 14 deletions(-)
>>
>> diff --git a/doc/README.rockchip b/doc/README.rockchip
>> index 2d8cf9f..229db0d 100644
>> --- a/doc/README.rockchip
>> +++ b/doc/README.rockchip
>> @@ -14,9 +14,6 @@ many Rockchip devices [1] [2].
>>   The current mainline support is experimental only and is not useful for
>>   anything. It should provide a base on which to build.
>>
>> -So far only support for the RK3288 and RK3036 is provided.
>> -
>> -
>>   Prerequisites
>>   =============
>>
>> @@ -26,17 +23,18 @@ You will need:
>>      - Power connection to 5V using the supplied micro-USB power cable
>>      - Separate USB serial cable attached to your computer and the Firefly
>>           (connect to the micro-USB connector below the logo)
>> -   - rkflashtool [3]
>> -   - openssl (sudo apt-get install openssl)
>> +   - rkdeveloptool [3]
> In my personal opinion, rkflashtool should stay. You can very well add
> rkdeveloptool as a second option, but rkflashtool was there first and
> also is the one that most distributions contain in their repositories.
> And both tools seem to have the same functionality.

OK, it can leave there, but I don't know why it does not works well with 
rk3399.

Thanks,
- Kever
>
>
> Heiko
>

[U-Boot] [PATCH] rockchip: doc: update latest info to document

[Heiko Stuebner]

Am Dienstag, 16. Mai 2017, 09:19:57 CEST schrieb Kever Yang:
> 
> On 05/16/2017 02:51 AM, Heiko Stübner wrote:
> > Hi Kever,
> >
> > Am Montag, 15. Mai 2017, 21:18:00 CEST schrieb Kever Yang:
> >> - Add some rk3399 and rk3328 boards;
> >> - use rkdeveloptool instead of rkflashtool;
> >> - use opensource.rock-chips.com instead of wikidot;
> >> - other update.
> >>
> >> Signed-off-by: Kever Yang <kever.yang@rock-chips.com>
> >> ---
> >>
> >>   doc/README.rockchip | 38 ++++++++++++++++++++++++--------------
> >>   1 file changed, 24 insertions(+), 14 deletions(-)
> >>
> >> diff --git a/doc/README.rockchip b/doc/README.rockchip
> >> index 2d8cf9f..229db0d 100644
> >> --- a/doc/README.rockchip
> >> +++ b/doc/README.rockchip
> >> @@ -14,9 +14,6 @@ many Rockchip devices [1] [2].
> >>   The current mainline support is experimental only and is not useful for
> >>   anything. It should provide a base on which to build.
> >>
> >> -So far only support for the RK3288 and RK3036 is provided.
> >> -
> >> -
> >>   Prerequisites
> >>   =============
> >>
> >> @@ -26,17 +23,18 @@ You will need:
> >>      - Power connection to 5V using the supplied micro-USB power cable
> >>      - Separate USB serial cable attached to your computer and the Firefly
> >>           (connect to the micro-USB connector below the logo)
> >> -   - rkflashtool [3]
> >> -   - openssl (sudo apt-get install openssl)
> >> +   - rkdeveloptool [3]
> > In my personal opinion, rkflashtool should stay. You can very well add
> > rkdeveloptool as a second option, but rkflashtool was there first and
> > also is the one that most distributions contain in their repositories.
> > And both tools seem to have the same functionality.
> 
> OK, it can leave there, but I don't know why it does not works well with 
> rk3399.

I'd guess most likely because it is missing the soc-specific id for
the rk3399 [0].


Heiko

[0] https://github.com/linux-rockchip/rkflashtool/blob/master/rkflashtool.c#L103