Jump to content

CSC Armbian for RK322x TV box boards

jock

By jock
in Rockchip CPU Boxes

 Share

Recommended Posts

jock

jock

Posted
  • Author
Posted
  On 11/26/2020 at 11:51 AM, megaduo said:

@fabiobassaYes,it is.

 

@jockUnfortunately，both of the overlays was not working，Thanks anyway.I decompress and decompiled the dtb file from the offical firmware.

    wireless-wlan {
        compatible = "wlan-platdata";
        wifi_chip_type = "rtl8189es";
        sdio_vref = <0x708>;
        WIFI,poweren_gpio = <0x7a 0x1d 0x00>;
        WIFI,host_wake_irq = <0x73 0x02 0x00>;

i'm trying to compile the overlay by dtc,but got an error,maybe missing some header？

  Reveal hidden contents

 

rk-kernel.dtb rk-kernel.dts

Expand  

I took a look to the device tree and it seems to me that the one of overlays I provided should work.

The gpio controlling the wifi chip power is gpio2-29 and so I set it in the overlays.

The decompilation and recompilation of device tree overlays is slightly different than regular device tree. Check this page, in particular the paragraph 2.1: Fragments. In short. you need the -@ argument to dtc to recompile the overlay back.

 

Anyway it would be very interesting to see dmesg when overlays are applied, to understand if the SDIO device is correctly recognized and there is an issue with the driver or the device still does not get recognized at all.

0
megaduo

megaduo

Posted
Posted
  On 11/26/2020 at 9:56 PM, jock said:

I took a look to the device tree and it seems to me that the one of overlays I provided should work.

The gpio controlling the wifi chip power is gpio2-29 and so I set it in the overlays.

The decompilation and recompilation of device tree overlays is slightly different than regular device tree. Check this page, in particular the paragraph 2.1: Fragments. In short. you need the -@ argument to dtc to recompile the overlay back.

 

Anyway it would be very interesting to see dmesg when overlays are applied, to understand if the SDIO device is correctly recognized and there is an issue with the driver or the device still does not get recognized at all.

Expand  

Here is the dmesg log

With overlays=wlan-8189etv-al

  Reveal hidden contents

With overlays=wlan-8189etv-ah

  Reveal hidden contents

 

0
jock

jock

Posted
  • Author
Posted
  On 11/27/2020 at 5:35 AM, megaduo said:

Here is the dmesg log

With overlays=wlan-8189etv-al

  Reveal hidden contents

With overlays=wlan-8189etv-ah

  Reveal hidden contents

 

Expand  

Mmmh, the overlays have been correctly loaded, I see the pwrseq using the gpio2-29 in both dmesg logs, but indeed the device is not detected.

Apparently there is something else in the recipe that is missing. I need some time to study the original dtb a bit better to understand what is wrong.

0
zero48

zero48

Posted
Posted
  On 11/26/2020 at 4:14 PM, fabiobassa said:

@zero48
perfet is a godness you have electronic skills
I suspect you have one fo the few, but very few hellish boards that use a particular trust os , so before attach any uart to ttl do this little test please:
copy this trust os into your card, you will need linux thought

 

SYNTAX is : dd if=/wheredoyouhavefile/trust-ddr2.img  of=/dev/thisisyoursdcard/ seek=24576

so if for example your sd is sdc and you have this file in /home/zero48 the whole syntax will be

 

dd if=/home/zero48/trust-ddr2.img of=/dev/sdc seek=24576  

of course you must unzip first the file
If this little test go wrong, well uart is our salvation :D

trust-ddr2.zip 684.07 kB · 0 downloads

Expand  

Got you .

 

I'll get a linux pc to my Bech and comeback to you ASP

 

Thanks once again 

0
jock

jock

Posted
  • Author
Posted

@megaduo I made a couple of other device tree overlays. Could not test them at all, just wrote them from scratch based upon the original device tree you provided. It appears that your box has a different wiring for SDIO, so not only the power pin is different but also the data/clock pins.

 

I attached them to this post, as usual put them in /boot/dtb/overlays directory and then change the overlays line in overlays=wlan-alt-wiring wlan-rtl8189etv  in /boot/armbianEnv.txt. Reboot and hope! :)

 

As usual, dmesg is appreciated for debug.

 

rk322x-wlan-alt-wiring.dtboUnavailable rk322x-wlan-rtl8189etv.dtboUnavailable

0
zero48

zero48

Posted
Posted
  On 11/26/2020 at 4:14 PM, fabiobassa said:

@zero48
perfet is a godness you have electronic skills
I suspect you have one fo the few, but very few hellish boards that use a particular trust os , so before attach any uart to ttl do this little test please:
copy this trust os into your card, you will need linux thought

 

SYNTAX is : dd if=/wheredoyouhavefile/trust-ddr2.img  of=/dev/thisisyoursdcard/ seek=24576

so if for example your sd is sdc and you have this file in /home/zero48 the whole syntax will be

 

dd if=/home/zero48/trust-ddr2.img of=/dev/sdc seek=24576  

of course you must unzip first the file
If this little test go wrong, well uart is our salvation :D

trust-ddr2.zip 684.07 kB · 3 downloads

Expand  

Hello, 

This is done check https://drive.google.com/file/d/1n1Th8yKMWPj11Za6ovvPn71NEk2JJMQw/view?usp=sharing

No joy, I suspect that my problem with these boxes is a booting issue  and that is why imagetool never have the chance to "Inflate" the FAT32 I guess .

TTL time ? Please advice  the next steps when time is right for you . I have several TTL converters and I'm use to Putty.

In another hands  just discovered this Thread from you 

Which would be my tonigh bed time history...

 

Thanks in advance 

 

Cesar

0
fabiobassa

fabiobassa

Posted
Posted

@zero48

No  way Cesar, it will work... it MUST work, now the problem is watch WHO will win, the board itself or ourselves !!!!

Ok ttl TIME. connect the converter,  on the board is clearly marked the tx and rx and SET the putty speed to 1500000 ( YES !! one million 500000 , thanks rockchip for this unusual speed)
you will see the very early booting of ddr ( it should say ddr3 330 mhz )  and some other things such as optee
Then the speed changes to usual 115200 so is bit problematic since you must close putty change speed and open back
I suggest to do this :
1)start the board and grab  log of putty at 1500000 until optee ( i hope you go at least to optee ) . close putty
2) set putty at 115200 reopen putty  and REBOOT board. You will see initial wrong characters since wrong speed but then the speed goes to right one
we need both logs one at 1500000 and the other at 115200

where you located Cesar ?

EDIT:
pleae grab also a full boot from Android , at 1500000

0
jock

jock

Posted
  • Author
Posted

@zero48

It would also be very nice to have the full original firmware, so we could inspect it and understand if there's something different with the Android 10 boot process. Maybe the box vendor gave you a link to the updated firmware or so... it would be very useful.

 

Maybe I lost some pieces behind, but when you insert the SDcard with the multitool what does exactly happens? The screen stays black or it just boots Android like usual?

0
jock

jock

Posted
  • Author
Posted
  On 11/28/2020 at 9:43 AM, fabiobassa said:

@jock

Based on our previous experiences with china producers ( 4 giga of ram, 64 gb of storage and the 2/16 really , or even worst..) would you put your hand on fire that really is android 10 inside ? :rolleyes:
:D

Expand  

Of course not :D Will keep my hands sane, I don't really want to discover if they put Android 10 in such a risky way :P

0
zero48

zero48

Posted
Posted
  On 11/28/2020 at 9:34 AM, jock said:

@zero48

It would also be very nice to have the full original firmware, so we could inspect it and understand if there's something different with the Android 10 boot process. Maybe the box vendor gave you a link to the updated firmware or so... it would be very useful.

 

Maybe I lost some pieces behind, but when you insert the SDcard with the multitool what does exactly happens? The screen stays black or it just boots Android like usual?

Expand  

I got these from a flea market locally ( Dominican Rep.) So far never researched for the android firmware.

When Insert the imagetool Sd card into the unit and power it on , it just stay there (both leds red and blue lite ) , Blue led does not Lite strong as when the Android normal boot does. I left once the SD card for 2 hours nothing happens, Screen stay as no video detected.( I did tried with both HDMI and HDMI to VGA adapter , same result).

 

Thanks

0
zero48

zero48

Posted
Posted
  On 11/28/2020 at 8:36 AM, fabiobassa said:

@zero48

No  way Cesar, it will work... it MUST work, now the problem is watch WHO will win, the board itself or ourselves !!!!

Ok ttl TIME. connect the converter,  on the board is clearly marked the tx and rx and SET the putty speed to 1500000 ( YES !! one million 500000 , thanks rockchip for this unusual speed)
you will see the very early booting of ddr ( it should say ddr3 330 mhz )  and some other things such as optee
Then the speed changes to usual 115200 so is bit problematic since you must close putty change speed and open back
I suggest to do this :
1)start the board and grab  log of putty at 1500000 until optee ( i hope you go at least to optee ) . close putty
2) set putty at 115200 reopen putty  and REBOOT board. You will see initial wrong characters since wrong speed but then the speed goes to right one
we need both logs one at 1500000 and the other at 115200

where you located Cesar ?

EDIT:
pleae grab also a full boot from Android , at 1500000

Expand  

Hi, 

I installed a male header and I'm using a PL2303TA USB to TTL Converter  https://drive.google.com/file/d/1YM3vGMn_nfofsoyjVoLueMcKZCMu3YxN/view?usp=sharing

Here attached 4 files , 2 of them normal Android boot other 2 with the SD card inserted, with 1.5m & 115200 speed respectively

However looks like there is a speed issue in my opinion, I did tested with 3 different TTL converters same result .

 

Well quite challenge. 

 

I'm from Dominican Republic.  -4GMT

 

Thanks

 

 

SDboot_1.5m.txtFetching info... SDboot_115200.txtFetching info... NoSD_115200.txtFetching info... noSD_1.5M.txtFetching info...

0
megaduo

megaduo

Posted
Posted
  On 11/27/2020 at 11:19 PM, jock said:

@megaduo I made a couple of other device tree overlays. Could not test them at all, just wrote them from scratch based upon the original device tree you provided. It appears that your box has a different wiring for SDIO, so not only the power pin is different but also the data/clock pins.

 

I attached them to this post, as usual put them in /boot/dtb/overlays directory and then change the overlays line in overlays=wlan-alt-wiring wlan-rtl8189etv  in /boot/armbianEnv.txt. Reboot and hope! :)

 

As usual, dmesg is appreciated for debug.

 

rk322x-wlan-alt-wiring.dtbo 1.21 kB · 6 downloads rk322x-wlan-rtl8189etv.dtbo 1.04 kB · 5 downloads

Expand  

Thanks for your reply，I tried both of overlays,but it's still not working.Is there any other way to find out the real gpio layout?

The dmesg with overlays=wlan-alt-wiring

  Reveal hidden contents

With overlays=wlan-rtl8189etv

  Reveal hidden contents

 

0
jock

jock

Posted
  • Author
Posted

@megaduo you had to use the overlays together, but anyway apparently I did a mistake in the wlan-alt-wiring because the kernel is complaining. Need to check it out first.

 

The easier way to get the real gpio layout is with device trees, otherwise you can X-ray scan the board and search for the copper paths from the SoC to the wifi chip, but I think it is far harder :P

 

0
fabiobassa

fabiobassa

Posted
Posted

@zero48
que diablura es esa? qual brujeria tiene esta board, ajajajaaj

Let's go back at english that is official and common language here, but let me say you live in my 3rd house : Italy, Cuba, Santo domingo !!

Ok back to board, definetly a speed issue or may be wrong pins, you just swapped tx and rx ? Ground = black I suppose is in right position , first on right
But I am also sure you already tried to swap them
The speed in normal android is 1 million 5 hundred thousand 1500000 did you check this ? may be missing a zero ?

0
zero48

zero48

Posted
Posted
  On 11/28/2020 at 4:32 PM, fabiobassa said:

@zero48
que diablura es esa? qual brujeria tiene esta board, ajajajaaj

Let's go back at english that is official and common language here, but let me say you live in my 3rd house : Italy, Cuba, Santo domingo !!

Ok back to board, definetly a speed issue or may be wrong pins, you just swapped tx and rx ? Ground = black I suppose is in right position , first on right
But I am also sure you already tried to swap them
The speed in normal android is 1 million 5 hundred thousand 1500000 did you check this ? may be missing a zero ?

Expand  

Well, "Naval captain does not become an expert in calm waters" was the first advice I got in my first Job at TV station just fresh out of Technical  High school. 

Next time you come to DR , Let me know, Dinner on me.

 

I Found a FTDI TTL converter which works almost perfect (definitively Prolific TTLs dont like that Speed)  I did not see any data @115200 so No Log at that speed . 

Everything it's a 1500000.

 

Here attached 2 files , with and witout SD card (notice that teh image in the card it is the trust-ddr2.img

SDboot_1.5m.txtFetching info...

I hope you may find something worth of value on these logsnoSD_1.5M.txt

 

Greetings from Santo Domingo 

 

 

0
fabiobassa

fabiobassa

Posted
Posted

@zero48

Check your private messages Cesar.

 

Anyway regarding your bootlogs, still something wrong because strange symbols appear .

Please check ground connection to uart or even better solder it.

I have pl 2303 and it goes  both on 115200 and 1500000

 

The board is booting and booting fine Cesar !!!!!

0
jock

jock

Posted
  • Author
Posted

@zero481.5 mbit/s has been always problematic even with my TTL converters, but your logs appear to me too much garbled with too many strange characters I never got.

Are you sure the ground pin is well connected?

 

Anyway, it looks to me that in both the logs just posted your box is booting Android, so no sdcard boot from what I see.

0
zero48

zero48

Posted
Posted
  On 11/28/2020 at 9:47 PM, jock said:

@zero481.5 mbit/s has been always problematic even with my TTL converters, but your logs appear to me too much garbled with too many strange characters I never got.

Are you sure the ground pin is well connected?

 

Anyway, it looks to me that in both the logs just posted your box is booting Android, so no sdcard boot from what I see.

Expand  

Hello, 

I'm in the process of soldering everything to avoid noise which probably is the cause as you pointed correctly.

SD card was inserted during one of the booting files . 

I'll be sending the results soon 

 

Thanks

0
zero48

zero48

Posted
Posted
  On 11/28/2020 at 9:46 PM, fabiobassa said:

@zero48

Check your private messages Cesar.

 

Anyway regarding your bootlogs, still something wrong because strange symbols happear .

Please check ground connection to uart or even better solder it.

I have pl 2303 and it goes  both on 115200 and 1500000

 

The board is booting and booting fine Cesar !!!!!

Expand  

Hello, 

 

No noise after soldering the TTL converter ... 

 

Here is 2 files , one with normal Android boot, teh other with imagetool (Sd card inserted) .SDboot_1.5m.txt

noSD_1.5M.txtFetching info...

 

Cesar

0
zero48

zero48

Posted
Posted
  On 11/29/2020 at 1:30 AM, zero48 said:

Hello, 

 

No noise after soldering the TTL converter ... 

 

Here is 2 files , one with normal Android boot, teh other with imagetool (Sd card inserted) .SDboot_1.5m.txt

noSD_1.5M.txt 103.17 kB · 0 downloads

 

Cesar

Expand  

A second SD card  (10 class both) :

DDR Version V1.09 20190628
In
ID:0xFFF
300MHz
DDR3
Bus Width=16 Col=11 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB
mach:2
OUT
Boot1 Release Time: Nov  9 2018 11:48:50, version: 2.54
ChipType = 0xc, 367
mmc2:cmd19,100
SdmmcInit=2 0
BootCapSize=2000
UserCapSize=7456MB
FwPartOffset=2000 , 2000
mmc0:cmd5,20
SdmmcInit=0 0
BootCapSize=0
UserCapSize=3774MB
FwPartOffset=2000 , 0
run on sd0
StorageInit ok = 938753
SecureMode = 0
SecureInit ret = 0, SecureMode = 0
GPT 0x632d7e00 signature is wrong
recovery gpt...
GPT 0x632d7e00 signature is wrong
recovery gpt fail!
tag:LOADER error,addr:0x2000
hdr 632d77e0 + 0x0:0x45435352,0x00000000,0x00010101,0x00000001,
 

0
jock

jock

Posted
  • Author
Posted

@megaduo

Here is the last one: rk322x-wlan-alt-wiring.dtbo

Put this in /boot/dtb/overlay and as usual put overlays=wlan-alt-wiring in /boot/armbianEnv.txt.

 

Note: the other 8189etv overlay is not needed anymore, wlan-alt-wiring is the only one you need.

 

I hope this works, otherwise I don't know where the problem could be.

 

PS: don't forget to paste a dmesg log even if the overlay works! In case it is successful I will include in the armbian installation ;)

 

0
megaduo

megaduo

Posted
Posted

 

  On 11/29/2020 at 1:54 PM, jock said:

@megaduo

Here is the last one: rk322x-wlan-alt-wiring.dtbo

Put this in /boot/dtb/overlay and as usual put overlays=wlan-alt-wiring in /boot/armbianEnv.txt.

 

Note: the other 8189etv overlay is not needed anymore, wlan-alt-wiring is the only one you need.

 

I hope this works, otherwise I don't know where the problem could be.

 

PS: don't forget to paste a dmesg log even if the overlay works! In case it is successful I will include in the armbian installation ;)

 

Expand  

Finally it's working!!!!!!!!Thanks a lot!!!!!!!

  Reveal hidden contents

@fabiobassaHere is photos of the borad.

11.thumb.jpg.9c6078baddb4ef23a0d6384f7aae71fc.jpg

22.thumb.jpg.f51be4dc6f4ec9d72b69f4e423b2886b.jpg

33.thumb.jpg.d7d8b14ec9296ff50d2e1de3f96a29df.jpg

 

0
jock

jock

Posted
  • Author
Posted

@zero48

Your sdcard log is truncated at some point. It seems that the internal bootloader stops before loading the necessary binaries from the sdcard  (see the LOADER error message...). It could happen though that the sdcard boots, switches the UART to 115200 bps and UART FIFO is flushed away, so we don't really get the latest messages.

 

Anyway me and @fabiobassa lately discovered an incompatibility with some existing boards and a part of the bootloader on the sdcard.

I just refreshed the multitool image with the incompatible code fixed, so you download it again from the first page and try again, maybe it solves your problem too

0
jock

jock

Posted
  • Author
Posted

@megaduo

Ah finally! I now see from dmesg that the SDIO device is correctly detected, but yet there is an error during the device probing.

Is the wifi working well for you?

0
megaduo

megaduo

Posted
Posted

@jockNot working,Maybe it's about the driver,I don't know what's meaning of error -110(rtl8189es: probe of mmc1:0001:1 failed with error -110) i'm gonna to compile the driver to check if it is working.

0
zero48

zero48

Posted
Posted
  On 11/29/2020 at 2:43 PM, jock said:

@zero48

Your sdcard log is truncated at some point. It seems that the internal bootloader stops before loading the necessary binaries from the sdcard  (see the LOADER error message...). It could happen though that the sdcard boots, switches the UART to 115200 bps and UART FIFO is flushed away, so we don't really get the latest messages.

 

Anyway me and @fabiobassa lately discovered an incompatibility with some existing boards and a part of the bootloader on the sdcard.

I just refreshed the multitool image with the incompatible code fixed, so you download it again from the first page and try again, maybe it solves your problem too

Expand  

That solved the problem !!

Now the SDcard it is accepting the image (testing with Focal which is bigger) flawlessly

 

  

 

Thanks very much to you and @fabiobassa for the support and patience 

 

Kudos !! 

 

image.png

1
jock

jock

Posted
  • Author
Posted
  On 11/29/2020 at 3:03 PM, megaduo said:

@jockNot working,Maybe it's about the driver,I don't know what's meaning of error -110(rtl8189es: probe of mmc1:0001:1 failed with error -110) i'm gonna to compile the driver to check if it is working.

Expand  

We're on the right way but maybe something still has to be refined.

I have another suggestion: take the two dtbo I gave you in this previous post, put them in the proper place.

Try first overlays=wlan-alt-wiring wlan8189-etv-ah and, if does not work, try overlays=wlan-alt-wiring wlan8189-etv-al in armbianEnv.txt

 

The error -110 is the standard linux error for timeout, so probably the sdio works because wlan-alt-wiring fixed the GPIO wiring of the bus, but the power enable GPIO pin has the inverted polarity (al=ACTIVE_LOW, ah=ACTIVE_HIGH) so we still need to catch this to let the wifi chip correctly being powered on.

 

edit: thanks for the photos, that's definitely not a board I have ever seen and does not resemble any of the common boards we encountered here on the forums.

 

0

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
 Share
Go to topic listing
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept