If you own one of these boards and would like to test and report issues, feel free to contact me via email at yyt@superkali.me or open an issue on GitHub Armbian or GitHub Armbian-YYT. Your feedback will help me improve the compatibility and performance of the board.
3. Frequently Asked Questions:
Why was only version v3 integrated and not v1?
Unfortunately, I don’t own the v1 version, so I can’t verify that everything works as expected. In theory, Armbian should work on v1, but some features might not be fully functional.
How can I contribute to the development?
You can help by testing the available versions, identifying bugs, and reporting issues using the links provided above. If you’re up for it, you can also submit pull requests, which will be reviewed and potentially merged into the mainline.
Is the current version considered stable?
Yes, versions are thoroughly tested before release, and we never release a version that would render the board unusable.
Do you plan to integrate retrogaming systems like Batocera?
Yes, my goal is to first fully optimize this board within Armbian and then begin development for Batocera.
For any other questions, feel free to comment below!
If you own one of these boards and would like to test and report issues, feel free to contact me via email at yyt@superkali.me or open an issue on GitHub Armbian or GitHub OpenSource-YYT. Your feedback will help me improve the compatibility and performance of the board.
3. Frequently Asked Questions:
Why was only version v3 integrated and not v1?
Unfortunately, I don’t own the v1 version, so I can’t verify that everything works as expected. In theory, Armbian should work on v1, but some features might not be fully functional.
How can I contribute to the development?
You can help by testing the available versions, identifying bugs, and reporting issues using the links provided above. If you’re up for it, you can also submit pull requests, which will be reviewed and potentially merged into the mainline.
Is the current version considered stable?
Yes, versions are thoroughly tested before release, and we never release a version that would render the board unusable.
Do you plan to integrate retrogaming systems like Batocera?
Yes, my goal is to first fully optimize this board within Armbian and then begin development for Batocera.
For any other questions, feel free to comment below!
Your feedback will help improve compatibility and performance.
Frequently Asked Questions
1. Why was only version v3 integrated and not v1?
Unfortunately, I don’t own the v1 version, so I can’t verify that everything works as expected. In theory, Armbian should work on v1, but some features might not be fully functional.
2. How can I contribute to the development?
You can help by testing available versions, identifying bugs, and reporting issues using the links provided above. If you’re up for it, you can also submit pull requests, which will be reviewed and potentially merged into the mainline.
3. Is the current version considered stable?
Yes, releases are thoroughly tested, and no version is released if it risks making the board unusable.
For any other questions, feel free to comment below!
Hey @SuperKali, and thank you very much for maintaining compatibility for that platform! Since you’re owning a v3, could you provide flashing instructions here, or point me to a place with working flashing instructions for MacOS (or Linux)? Just a description of how you perform that task would already be super helpful cause the official documentation was not helping at all.
Edit: For any weary traveler passing by here, I’ve eventually figured out what to do. Here comes the step-by-step guide how to flash Armbian to the YouYeeToo R1 using MacOS:
Clone rkdeveloptool from github and patch using these instructions to fix a compatibility issue with clang (the code is written to be compiled with gcc; you can also just compile with gcc if you don’t mind the additional 500MB installation size on your machine and the binary being linked against an additional lib).
Install required packages using brew and then build & “install”: brew install automake autoconf libusb pkg-config git wget cd rkdeveloptool autoreconf -i ./configure make -j $(sysctl -n hw.ncpu) cp rkdeveloptool /opt/homebrew/bin/
Switch the little OTG-switch on the bottom of the R1 to position “1”
Before powering on the R1, get a cursed USB-A-male-to-USB-A-male cable and use a USB-A-to-C-adapter at one end to connect it to your MacBook. Plug the other USB-A-male end into the blue USB-A port on the R1. There might be cursed USB-A-male-to-USB-C cables, but I have found none.
It is important that you have plugged in the cursed cable before powering up the R1.
Power up the R1 while holding the “Recovery” mini button at the side and release it after a few seconds. The R1 should start with the red and green indicator LEDs at the side constantly lit up.
Do a rkdeveloptool ld in you terminal. You should get something like DevNo=1 Vid=0x2207,Pid=0x350b,LocationID=1 Loader
First erase flash: rkdeveloptool ef
Then flash whatever compatible OS you like. I’m using the Armbian community build: rkdeveloptool wl 0 Armbian_community_26.2.0-trunk.332_Youyeetoo-r1-v3_forky_current_6.18.7_minimal.img
Once the flash is complete, unplug the cursed USB cable, and either power cycle or reset the CPU with the “Reset” mini button at the side of the R1.
Congratulations! You have successfully flashed the R1 using MacOS.
Important gotchas:
The rkdeveloptool won’t built with clang unless you patch it as described.
You have to use a cursed cable. Regular USB-A-to-C won’t work.
The cursed cable has to be plugged in before you power up the R1 or it won’t enter Maskrom mode.
If you’ve messed up the eMMC and can’t get the RK3588s into Loader mode anymore, start it into Maskrom mode holding the “Boot” instead of the “Recovery” button. You don’t need to have the cursed USB cable plugged in during startup. When the devise has successfully booted into Maskrom mode, it should say so when calling rkdeveloptool ld, with the two control LEDs on the R1 constantly lit up. Now first flash a working loader (this one worked for me): rkdeveloptool db rk3588_spl_loader_v1.15.113.bin
After that you should be able to proceed from step 8 on.
