Jump to content

[Armbian build PR] - Helios64: memory is unstable without the rockchip ddr blob


Recommended Posts

Posted

Description

Switch back to Rockchip DDR binary for DDR initialization in u-boot for Helios64.

I believe there is nothing board-specific about this memory initialization issue, but it might be no other Armbian board has this combination of rk3399 and LPDDR4.

Else there is something specific about the memory set up on the Helios64 hardware.

On the Helios64 random memory errors happens when using the U-Boot DDR intialization code for rk3399. Switching to the rkbin rk33 933MHz v1.25 allows this testcase to run more than once without a memory error: for i in $(seq 1 100);do python3 -c "import pkg_resources" || break;done

Could be LPDDR4 specific.

Workaround https://github.com/armbian/build/issues/4761 "free() invalid pointer".

A proper fix would be to fix u-boot own lpddr4 initialization code for Rockchip but I miss the Rockchip DDR binary settings to compare with.

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration.

  • [ x ] run for i in $(seq 1 100);do python3 -c "import pkg_resources" || break;done multiple times

Checklist:

  • [ x ] My code follows the style guidelines of this project
  • [ x ] I have performed a self-review of my own code
  • [ ] I have commented my code, particularly in hard-to-understand areas
  • [ ] I have made corresponding changes to the documentation
  • [ x ] My changes generate no new warnings
  • [ x ] Any dependent changes have been merged and published in downstream modules

View the full article

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines