Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: FriendlyARM NanoPC T4 DDR unstable #7754

Closed
1 of 2 tasks
msdos03 opened this issue Jan 27, 2025 · 3 comments
Closed
1 of 2 tasks

[Bug]: FriendlyARM NanoPC T4 DDR unstable #7754

msdos03 opened this issue Jan 27, 2025 · 3 comments
Labels
Bug Something isn't working as it should Not framework bug Bug in 3rd party component

Comments

@msdos03
Copy link
Contributor

msdos03 commented Jan 27, 2025

What happened?

FriendlyARM official system images all run fine.

"memtester" in armbian and mtest in u-boot don't report any error, but when I am using a browser or running a java virtual machine, it crashes frequently. After some tests on the u-boot, I found the issue is related to RAM.

If I use 800MHz DDR blob or modify rk3399-nanopc-t4-u-boot.dtsi in u-boot to include rk3399-sdram-lpddr3-4GB-1600.dtsi instead of rk3399-sdram-lpddr3-samsung-4GB-1866.dtsi , The problem is solved.

That make sense to me because FriendlyARM official system images are all using 800MHz DDR blob.

So, I suggest change the DDR blob to 800MHz one, or switch to blobless and add a patch to apply the mentioned modification.

How to reproduce?

It is hard to reproduce on other boards because the RAM chips and board revision are diffrent. On my board, installing java and run a large program or browsing the internet for a while can reproduce the problem.

Branch

main (main development branch)

On which host OS are you running the build script and observing this problem?

Ubuntu 24.04 Noble

Are you building on Windows WSL2?

  • Yes, my Ubuntu/Debian/OtherOS is running on WSL2

Relevant log URL

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@msdos03 msdos03 added the Bug Something isn't working as it should label Jan 27, 2025
Copy link
Contributor

github-actions bot commented Jan 27, 2025

Jira ticket: AR-2594

@mr-toolcraft
Copy link
Contributor

While this issue tracker is officially for framework problems only (building Armbian to say), I'd say to leave it here for now since ideally OP could provide a PR with the mentioned changes and link this issue.

Did you try both ways blobless and with the 800 blob?

@igorpecovnik igorpecovnik added the Not framework bug Bug in 3rd party component label Jan 27, 2025
@msdos03
Copy link
Contributor Author

msdos03 commented Jan 27, 2025

While this issue tracker is officially for framework problems only (building Armbian to say), I'd say to leave it here for now since ideally OP could provide a PR with the mentioned changes and link this issue.

Where should I place this issue?

Did you try both ways blobless and with the 800 blob?

Yes, I've tried both ways, they both work fine. Note that we need to patch rk3399-nanopc-t4-u-boot.dtsi in blobless.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working as it should Not framework bug Bug in 3rd party component
Development

No branches or pull requests

3 participants