Posts by rawnar

Observations made while using the LE 13 test image on the Wetek Hub.

• Subtitles are not working.
• Booting and shutting down takes longer then expected. After the splash image of LibreElec a black screen with only the version number in the top left corner is shown for at least 20 seconds.
• When starting a movie, the screen first goes black (probably the HDMI clock thingy), then it often returns after a few seconds showing the loading indicator and after another short period the movie starts. (x264 encoding)
• Once the screen did not came back and I had to re-plug the HDMI cable to see that the movie had started. (x264 encoding)
• Starting a second movie after stopping the first one the movie hangs for minutes before continuing. (both x264 encoding)
• When a movie is paused first the video output stops, then it plays for one second, and then is stops. (x264 encoding)

I will try to capture some dmesg output.

Quote from chewitt

rawnar I've also included a WeTek Hub image in the test share. Apologies for the long wait, I got a bit distracted.

Found it. You beat me to it. I almost had my old linux installation up and running again to build the image myself.

I placed it on a SD-Card and booted the system. Attached you can find the output I recorded from the UART. Spoiler: No strange characters coming from the UART and the system has booted now several times without halting during boot. So, the fix you made 1 year ago works .

Other thinks you like to see tested on the Wetek Hub?

I do think I need a image build for the wetek-hub to perform the test.

I wiped the emmc and tried to boot from a SD-Card. But ended up with a system that is constantly resetting. I think it is loading the U-boot from the SD-Card, but is unable to initialize the DDR. See the serial output in the attached text file. The Wetek play2 and Wetek Hub differ in the amount of work memory they have.

I found an old LE 11.0.6 wetek-hub image and that one did boot, but clearly had problems with the UART. It stopped the autoboot process because of an interrupt. After giving the boot command it went on with the boot process and I got into the command console. But after every command given extra characters were returned over the UART. So, I now know what not faulty behavior is. .

The back-up image has been downloaded. Now that I re-read your previous message's, I see the mistake I made. I will try it again. So just to be clear, I can clear the emmc using the following command LibreELEC:/ # emmctool zero. After which I can boot using the "wetek-play2" image installed on a second SD-Card using the LibreElec USB-SD creator. Right?

Optionally I can make a back-up of my current installation using LibreELEC:/ # emmctool backup backup-emmc and then after testing put is back using LibreELEC:/ # emmctool write backup-emmc.

Small comment on the emmctool scripts. I think that for the backup command the b option is missing on line 217.

case "${1}" in
  backup)
    do_backup "$@"

should probably be

case "${1}" in
  backup | b)
    do_backup "$@"

I managed to get some console output through the serial line using putty. (btw serial setting I used were 115200n8). You can find them in the attached zip-file. I have logged different runs.

1. dtech image installed on the EMMC.
2. chewitt box image installed on a SD-Card.
3. chewitt wetek play2 image installed on a SD-Card (2 times)

One thing that I see is that for the "wetek play2" image the KERNEL is not loaded as U-Boot can not find it. And therefor it falls back to a Android kernel. The following lines indicate that.

reading kernel.img
** Unable to read file kernel.img **
<<-->>
reading aml_autoscript
** Unable to read file aml_autoscript **
reading recovery.img
** Unable to read file recovery.img **
<<-->>
## Booting Android Image at 0x01080000 ...
<<-->>
[    0.000000@0] Linux version 3.14.29 (alex@alex-laptop)

On the box version U-Boot seems to use the s905_autoscript to find the KERNEL. Do I need to add some files from the "box" image to the "wetek play2"image to load the KERNEL? Or do you now have the information you need?

Oh and that I do not always get output to the HDMI seems to be related to U-boot finding the wrong hdmi mode. 1080p60hz having output and smpte24hz having no output.

Results so far.

Booting from a SD-Card using the LE 12.90.1 "box" image gives no problem. It boots normally one can watch videos.

Booting from a SD-Card using the "wetek-play2" image and changing the extlinux.conf to point to the device-tree of the wetek hub did not work. Tried it five times using the toothpick method (reset button pressed for 4-5 seconds), but every time the HDMI output is switched off after the Wetek splash-screen went away. The first time the screen came back showing some kind of boot menu, but the other four times the HDMI output stayed off.

Okay I will first do some tests booting from the SD card. When I have the results I will post them here.

Good luck with the Rockchips.

chewitt: I have made the SD card using the "box" image. Where can I find the "wetek-hub" board image? In your testing folder I can find the "wetek-play2" and "wetek-core2" board images, but not the "wetek-hub" one. Can I use the "wetek-play2" board image?

Did some digging through the boxes and found the original UART to DB9 cable. I assume it uses RS232 levels for the serial communication.

Quote from chewitt

I'm also interested to hear if WeTek Hub boards are booting fine now? - some folks had an issue we suspected of being noise on the UART that caused it to see a keypress and enter the u-boot console instead of booting. Feedback would be nice.

As a Wetek Hub owner I can try to test this for you. I have some experience with linux and command-line. Is there a way to verify that the issue is solved? Can one for instance monitor the UART activity once the system has been started? Or do I just need to start the system multiple times and see what happens?