public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Paweł Jarosz" <paweljarosz3691@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] u-boot Boot issue about rk3188
Date: Tue, 26 Sep 2017 13:34:28 +0200	[thread overview]
Message-ID: <aae7e315-654d-daef-b95d-dfc789850ddb@gmail.com> (raw)
In-Reply-To: <1645025.AkBsBVexX4@diego>

Hi,


W dniu 25.09.2017 o 12:29, Heiko Stübner pisze:
> Hi Andy,
>
> Am Montag, 25. September 2017, 17:45:03 CEST schrieb Andy Yan:
>> On 2017年09月22日 13:56, Heiko Stuebner wrote:
>>> Am Freitag, 22. September 2017, 08:50:49 CEST schrieb Andy Yan:
>>>> Hi Heiko:
>>>>
>>>> On 2017年09月22日 08:24, Andy Yan wrote:
>>>>> Hi Heiko:
>>>>>
>>>>> On 2017年09月21日 22:55, Heiko Stübner wrote:
>>>>>> Hi Andy,
>>>>>>
>>>>>> Am Donnerstag, 21. September 2017, 22:03:32 CEST schrieb Andy Yan:
>>>>>>> Hi Heiko:
>>>>>>> I try to boot the upstream u-boot-rockchip branch  on my rk3188 board
>>>>>>> with(rock_defconfig)
>>>>>>>
>>>>>>> But I got this error:
>>>>>>> early_init()
>>>>>>> nit_and_scan() returned error -22
>>>>>>> early_init() failed: -22
>>>>>>> ERROR ### Please RESET the board ###
>>>>>>>
>>>>>>> the current commit head is: 782088d("rockchip: imply ADC and
>>>>>>> SARADC_ROCKCHIP
>>>>>>> on supported SoCs") Do you ever meet something like this?
>>>>>> that is very strange. When testing Philipp's branch, I was also
>>>>>> testing the
>>>>>> commit you mention to see if anything broke since I last changed u-boot
>>>>>> on my radxa rock. And the above commit started just fine, when starting
>>>>>> from an sd-card.
>>>>>>
>>>>>> Not sure from which medium you're starting though. But from what I
>>>>>> remember Pawel got nand working in his rk3066 series, but that is not
>>>>>> yet merged.
>>>>>>
>>>>>       I boot from emmc, I will go on hack on it.
>>>>>       
>>>>        I finally can boot it with the rock_defconfig. But the way to
>>>>
>>>> package the tpl spl u-boot a little different.
>>>>
>>>>        cat ${DIR}/out/tpl/u-boot-tpl.bin > tplspl.bin
>>>>        truncate -s 1020 tplspl.bin
>>>>       
>>>>       sed -i "/^/{1s/^/RK31/}" tplspl.bin
>>>>       cat ${DIR}/out/spl/u-boot-spl.bin > spl.bin
>>>>       truncate -s %2048 spl.bin
>>>>       cat spl.bin >> tplspl.bin
>>>>       
>>>>       Then the tplspl.bin + u-boot.bin should package by
>>>>
>>>> boot_merger(tplsplb.in for FLashData, u-boot.bin for FlashBoot) from
>>>>
>>>> rockchip downstream u-boot repo:
>>>>       ./tools/boot_merger ./tools/rk_tools/RKBOOT/RK310BMINIALL.ini
>>>>       
>>>>       download to emmc by "upgrade_tool ul" command. According to our
>>>>
>>>> bootrom code author, the rk31(maybe include rk30) bootrom has a
>>>> limitation that the idbblock
>>>> couldn't accessed by upgrade_tool wl command.
>>> I do have a script handling that [0]. At least for the sd-card variant
>>> a simple "openssl rc4" works just as well as the legacy boot_merger :-)
>>>
>>> Heiko
>>>
>>> [0]
>>> https://github.com/mmind/u-boot-rockchip/commit/81458bde873d6cf588e082ccf
>>> 556e818f46ad9df
>>      Is there a way to download the out that generated by[0] to
>> emmc/flash? It seems that the upgrate_tool can't access 0x40 of the
>> emmc/nand on rk3188.
>>
>> you have the @rock-chips.com address, so I'd guess you might even have
>> the better resources to find out ;-)  .
>>
>> In any case, as I said I haven't looked at all at the internal storage on
>> my radxarock so far.
>>
>> But as the rk3066 and rk3188 are so similar I've added Paweł.
>>
>> @Paweł: you had uboot starting from nand on your rk3066 board, maybe you
>> could describe how you wrote it to the board so maybe Andy can check if
>> he needs to adapt anything?
Almost all knowledge i had about rk3066 boot process was from Heiko and 
bootrom disassembly.

Andy, do you have any output on serial console ? (TPL, Uboot-spl or 
anything else)
Can you compile u-boot with #define DEBUG in rk3188_common and send the 
output?
Also you can check size of u-boot tpl (less than 1kb), u-boot spl + tpl 
(less than sram size on rk3188, i think it's 32KB)? This is important as 
you wont get any output on serial console if you don't meet this conditions.
Also on rk3066 bootmerger FlashBoot size + FlashData size should be less 
than 256KB (32KB for FlashData, and the rest for FlashBoot, if it's more 
than 256KB, you get few lines of errors when flashing with upgrade_tool 
and might have no output on serial console)

One more thing ... to boot from usb with openssl rc4 method on rk3066 i 
think only one back to bootrom is needed, two if you are booting from nand.

Cheers
Paweł
> Thanks
> Heiko

  parent reply	other threads:[~2017-09-26 11:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-21 14:03 [U-Boot] u-boot Boot issue about rk3188 Andy Yan
2017-09-21 14:55 ` Heiko Stübner
2017-09-22  0:24   ` Andy Yan
2017-09-22  0:50     ` Andy Yan
2017-09-22  5:56       ` Heiko Stuebner
2017-09-25  9:45         ` Andy Yan
2017-09-25 10:29           ` Heiko Stübner
2017-09-25 11:49             ` Andy Yan
2017-09-25 12:48               ` Heiko Stübner
2017-09-26 11:34             ` Paweł Jarosz [this message]
2017-09-27  1:48               ` Andy Yan
2017-09-27  6:55                 ` Paweł Jarosz
2017-09-27  7:46                   ` Andy Yan
2017-09-27  8:38                     ` Paweł Jarosz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aae7e315-654d-daef-b95d-dfc789850ddb@gmail.com \
    --to=paweljarosz3691@gmail.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox