Hi Marek,
On 2/12/25 1:32 PM, Belisko Marek wrote:
Hi,
On Fri, Jan 24, 2025 at 11:30 AM Marek Belisko via lists.yoctoproject.org
<marek.belisko=gmail....@lists.yoctoproject.org> wrote:
Hi Quentin,
On Fri, Jan 24, 2025 at 11:15 AM Quentin Schulz <quentin.sch...@cherry.de>
wrote:
Hi Marek,
On 1/24/25 11:04 AM, Marek Belisko via lists.yoctoproject.org wrote:
Hello,
I'm trying to add support for rk3328-evb. I've added a machine and
built a
minimal image which I would like to flash to emmc. For flashing I'm
usually
using rkdeveloptool which download some binary blok (loader) and then
can
flash wic image (at least I'm doing that for radxa boards). Does anybody
have an idea where I can find such loader pls? I've tried this :
https://xdaforums.com/attachments/for-rk3328-devices-rar.5168743/ but
none
of them works (it prints: Opening loader failed, exiting download
boot!).
I've tried to use MiniLoaderAll.bin from the vendor but this one just
prints some garbage to the serial port and I cannot download wic after
that.
I do not have any RK3328 board available, but the instructions so far
are the same for RK3399, PX30 and RK3588 (the boards I do have access to).
https://github.com/rockchip-linux/rkbin
tools/boot_merger RKBOOT/RK3328MINIALL.ini
This will generate an rk3328_loader_v1.21.250.bin file at the root of
rkbin directory. Use that as argument for `rkdeveloptool db` command.
Thanks a lot for that.
I made build from meta-rockchip with added rk3328 machine (basically copy
of some other 3328) and was able to flash it but TPL hangs in following way:
U-Boot TPL 2022.01 (Jan 10 2022 - 18:46:34)
data training error
col error
data training error
DDR3, 333MHz
BW=16 Col=12 Bk=8 CS0 Row=16 CS=1 Die BW=8 Size=4096MB
It's some vendor custom board and they don't provide support but from what
I understand it's just close of evk.
Do you have some idea what should be checked before I dig into the u-boot?
Thanks
Multiple possible issues:
- TPL is too big and doesn't fit into SRAM (hence execution just stops
at some point because it's lacking code)
- TPL does not return to BROM (BootROM) after it's finished and tries to
continue to SPL but SPL isn't loaded,
- TPL returns to BROM but the BROM isn't capable of handling that,
- idbloader.img is improperly generated (e.g. the header, the alignment,
the size or location of TPL/SPL is improper),
I would suggest to maybe check with upstream vanilla U-Boot instead of a
3 years old vendor tree. 2022.01 means it is NOT based on Rockchip's
horrendous U-Boot tree, so there's some chance it isn't going to require
a lot of deep knowledge to port support for your board upstream. Failing
that, I would try to add a few prints here and there in the TPL code,
though be careful, it may drastically increase the size of the TPL and
make it not fit in SRAM. Additionally, if it already doesn't fit in
SRAM, adding print statement may trigger different behavior that may be
seen as progress while it's just moving code around (e.g. compiler
optimization).
You could also ask for help on the U-Boot mailing list, there are a few
contributors quite active on Rockchip-based boards and maybe they'll be
able to help with that.
Cheers,
Quentin
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#64819): https://lists.yoctoproject.org/g/yocto/message/64819
Mute This Topic: https://lists.yoctoproject.org/mt/110787954/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
