CSC Armbian for RK3318/RK3328 TV box boards

[jock]

@paradigman try looking here for latest rockchip64 kernel headers, but I'm not sure the version will match.

Usually I install the kernel headers via regular apt, so don't know if armbian-config is ok or is broken.

[paradigman]

@Jean-Francois Lessard: First of all, I would like to thank you for your great work with the tm16xx display driver.
I would like to ask for your help on how I can avoid the warnings below when compiling?
 

scripts/Makefile.build:403: warning: overriding recipe for target 'built-in.a'
Makefile:1168: warning: ignoring old recipe for target 'built-in.a'
scripts/Makefile.build:418: warning: overriding recipe for target 'modules.order'
Makefile:1848: warning: ignoring old recipe for target 'modules.order'
scripts/Makefile.build:403: warning: overriding recipe for target 'built-in.a'
Makefile:1168: warning: ignoring old recipe for target 'built-in.a'
scripts/Makefile.build:418: warning: overriding recipe for target 'modules.order'
Makefile:1848: warning: ignoring old recipe for target 'modules.order'
scripts/Makefile.build:403: warning: overriding recipe for target 'built-in.a'
Makefile:1168: warning: ignoring old recipe for target 'built-in.a'
scripts/Makefile.build:418: warning: overriding recipe for target 'modules.order'
Makefile:1848: warning: ignoring old recipe for target 'modules.order'
scripts/Makefile.build:403: warning: overriding recipe for target 'built-in.a'
Makefile:1168: warning: ignoring old recipe for target 'built-in.a'
scripts/Makefile.build:418: warning: overriding recipe for target 'modules.order'
Makefile:1848: warning: ignoring old recipe for target 'modules.order'

 

[paradigman]

@Jean-Francois Lessard : could you share with us the compiled objects (*.o) and the kernel object (*.ko)?
I have been unable to compile kernel on armbian for a week because there is some general error at the system level (kernel headers).

Edited February 16 by paradigman

[Jean-Francois Lessard]

@paradigman it looks like an issue with your kernel build system, not the display driver. The kernel build system is either packaged with the kernel source code or the kernel headers of your very specific kernel version. Since the compiled module is once again specific to your kernel version, sharing compiled objects won't be of any help. Try to fix your kernel build system first.

[paradigman]

Can someone help me how I can fix my kernel build system? Whatever image I flash on my board, the armbian-config -> "install kernel headers" function does not install everything needed to compile the kernel.

[ROOD]

@jock Hey!  Thanks for all your effort trying to bring Armbian to the TV Boxes. I wanted to ask if there was a chance to port it to the BQEEL U1 PRO, it has the RK3328 CPU.

I totally screwed the flash up doing some experiments and i couldn't get the flash backup so im kinda lost on that front. 
I tried to download the images from the first link but every link is broken.

I wonder if there is a mirror or any other way to get the images
Tried searching for them elsewhere but got nothing but a very weird image This one that kind of works but it just blinks the led blue and red without any Video output.
Maybe its just a dtb issue but im too new to fully understand and fix the issue


Edit:
I was able to boot using the Multitool and tried to burn an image to EMMC but now it doesn't boot with either option.

I tried to short the pins like Constantin did here Very similar board if not the same but couldn't get it to boot, maybe im missing something....

Here are some images 

Edited yesterday at 03:49 AM by ROOD

[otus]

Hey
Try to search for the image on:
https://github.com/armbian/community/releases
Maybe try:
https://github.com/armbian/community/releases/download/25.5.0-trunk.87/Armbian_community_25.5.0-trunk.87_Rk3328-heltec_noble_current_6.12.15_gnome_desktop.img.xz

[ROOD]

@otus thanks for the link and advice. At this moment I'm even struggling to get to boot from SD
I was following a guide and it told me to write the image to the Flash and now i cant even get the Multitool to boot from SD. I tried to use the EMMC pins method but either i did it wrong or i dont know what im doing. I shorted those pads with a dupont jumper wire and plugged in the power then unshorted it but nothing seems to happen when i do that

[jock]

@ROOD your board (YX_RK3328) should be already supported by rk3318-box image. The "marketing name" of the TV Box means nothing, the only important discriminant is the board name printed on the PCB.

 

Anyway you made two mistakes:

•  took the image from an unkown source
• burnt a non-working image in eMMC

Now your only chance to restore board functionality is to go in maskrom mode: eMMC is always first priority, so you don't have any chance to boot from SDcard if a image that does not boot is stored in eMMC.

[ROOD]

@jock Hey, yeah... i messed up big time hehe

So.. i made my own DIY Male to Male USB, used the pads suggested by Constantin and i was able to boot into maskrom mode, at least it says it found a device when i plug it in.

 

Using RKDevTool v2.86 i get the prompt that it found the device but nothing works, i cant seem to do anything with it, not sure what im doing wrong.

[jock]

@ROOD good

Important premise: when you short the pads you're actually excluding the eMMC from boot, so the SoC will boot from sdcard and, if there is no sdcard, then will go in maskrom waiting for something. 

Hence you have different options:

• burn the multitool on sdcard, then insert the sdcard and turn on the board with pads shorted. The multitool should boot and then you can erase the eMMC
• burn a good image (use the @otus links) onto the SDCard and boot (with pads shorted) Armbian from sdcard. Once booted, then erase the eMMC with dd (first 4 megabytes will sufficed) or with blkdiscard
• upload a loader with RkDevTool (or rkdeveloptool from Linux, without uploading a loader you won't be able to do anything; you should be able to find it in first page or somewhere in this thread, can't remember...), then erase the eMMC

The first option seems the easiest to me.

Once you erase the eMMC, the board will boot from sdcard and you can test a valid Armbian image.

Obviously burn an image onto eMMC only when you're sure it boots from sdcard.

 

You can get access to the TTL serial uart from the three aligned pins that lay between the LCD display and the USB 3.0 port, if you have a serial adapter of course.

Also, don't trust too much the eMMC: these particular boards were affected by bad eMMC/soldering iron that often caused it to fail.

[ROOD]

@jock after much suffering i was able to boot the multitool and delete the emmc image, i can now boot into the multitool without having to short the pads.
Now...  i need to find a suitable image for my board...
Downloading...  Armbian_community_25.5.0-trunk.87_Rk3318-box_bookworm_current_6.12.15_minimal.img
Flashing....
Done...
Booting....

HOLY it worked lol!
Im at the login screen... im guessing the default is something like "root"  "1234" or similar.
Now i need to write the image to the emmc... 

EDIT:

The image seems to work but for some reason when connected to my tv i tried to connect to wifi and the image started to stutter  i couldn't get it to connect to wifi but it did see my network. weird... need to keep trying i guess

Edited 11 hours ago by ROOD
added info

[jock]

@ROOD ok that's fine, yes default credentials are root:1234

You probably may go burning on eMMC, surely it won't brick and you should be able to run multitool or armbian on sdcard to handle maintenance if you need; I would anyway first configure the board with rk3318-config script and, when you found an optimized and stable setup, then burn on eMMC and replicate the setup

[ROOD]

@jockIf i have an image already on the EMMC will i be able to boot from multitool without shorting the pads? Or since i'll have a working EMMC boot it will no longer boot from SD?

[jock]

15 minutes ago, ROOD said:

@jockIf i have an image already on the EMMC will i be able to boot from multitool without shorting the pads? Or since i'll have a working EMMC boot it will no longer boot from SD?

Normally it should work this way: armbian bootloader (u-boot) priority was first to sdcard, then USB stick, and finally eMMC.

Recently (months ago) I bumped to a newer version of u-boot and there was some people reporting that the priority somehow changed, but I had no time to check it by myself; so take that with a grain of salt.

[ROOD]

@jock Everything seems to be working "fine" from the SD Card but so far after using rk3318-config and choosing the YX board, while i get Wifi it doesn't connect, i can see the networks (sometimes it says that the resource is busy) but even when i plug in the SSID and Password it just goes back to the menu and doesn't work.

 

Right now i was able to access it via Ethernet and SSH so that works as intended.

 

 

EDIT:

Tried to get some more info and it seems that there is a driver issue, dmesg gives me the following output
Did a search for that.blob file but couldn't find it, maybe i could get it from a Stock rom?

Edited 4 hours ago by ROOD