Jump to content

Recommended Posts

Posted (edited)
  On 7/13/2022 at 3:02 PM, jock said:

@Gausus You'd better try a specialized memory benchmark application like mbw rather than involving the linux filesystem subsystem and dd to do such kind of benchmarks.

Expand  

 

Thank you for the tips @jock

 

 

I have 2 H96max+ RK3328 โˆ• 4GB  tvboxes.

 

Armbian 22.08 - Debian Bullseye minimal - mainline kernel 5.18.10

 

BOX1 :  On internal eMMC

BOX2:   Boot Armbian from SDCARD  , Android on internal eMMC

 

Benchmark from terminal:

mbw 1000

 

Box1 : RAM 667Mhz CPU @ 1,3GHz

AVG    Method: MEMCPY    Elapsed: 0.82118    MiB: 1000.00000    Copy: 1217.764 MiB/s
AVG    Method: DUMB    Elapsed: 0.88632    MiB: 1000.00000    Copy: 1128.263 MiB/s
AVG    Method: MCBLOCK    Elapsed: 0.27756    MiB: 1000.00000    Copy: 3602.800 MiB/s

 

Box2 : RAM 333Mhz (Android uboot) CPU @ 1,3GHz

AVG    Method: MEMCPY    Elapsed: 1.51033    MiB: 1000.00000    Copy: 662.107 MiB/s
AVG    Method: DUMB    Elapsed: 1.62614    MiB: 1000.00000    Copy: 614.955 MiB/s
AVG    Method: MCBLOCK    Elapsed: 0.54709    MiB: 1000.00000    Copy: 1827.854 MiB/s

 

To boot from sdcard when Android on internal storage.

1. Flash Armbian on sdcard

2. Download Multitool.img 

3. Mount multitool.img on linuxpc or flash to another sdcard.

4. Copy  trustos.img and uboot.img from bsp folder to a folder on linuxpc,

5 . DD trustos.img and uboot.img to sdcard Armbian from linuxpc

 

sudo dd if=uboot.img of=/dev/SDCARD seek=16384 conv=fsync
sudo dd if=trustos.img of=/dev/SDCARD seek=24576 conv=fsync

 

 

 

Edited by Gausus
Posted
  On 7/12/2022 at 11:01 AM, jock said:

Sorry for the bad experience ๐Ÿ˜ฅ

Expand  

No prob, I was counting on the possibility of bricking it, but it was just a 20โ‚ฌ crappy device laying around. And it is not bricked after all, yet it works faster than factory with Armbian, and even have WiFi, which I didn't expect ๐Ÿ˜†

I'm on vacation and I don't have any USB-OTG cable here, so I cannot use the RK flashing tool. There is an option to create an "upgrade SD card", but it only supports cards up to 16GB, not bigger (WTH?), and also requires a reset button which seems not to be present on the device.

 

This also motivates me to spend some time finishing the media integration for Mainline, so I can at least use Kodi on this ๐Ÿ˜„

 

Posted
  On 7/13/2022 at 6:46 PM, JMCC said:

This also motivates me to spend some time finishing the media integration for Mainline, so I can at least use Kodi on this ๐Ÿ˜„

Expand  

I have some old notes about compiling ffmpeg, kodi and mpv for mainline. ffmpeg and mpv worked out really well, kodi was bit of hit and miss.

If you need a hand with that I may send you those things.

Posted
  On 7/14/2022 at 3:58 PM, jock said:

I may send you those things

Expand  

Sure, you can PM them to me, please.

 

On a side note, I finally got to re-flash some image to my TV box, using a usb-c to usb-a cable on my laptop. This one seems to make the box run a bit hotter and maybe faster, I will try to investigate whether memory is clocked at 666MHz or not.

[EDIT: No, all dmc opp's 400MHz and above are disabled. But the CPU opp at 1104MHz is runnig at a voltage of 1275/1275/1350, hence the heat. This is crazy...]

Posted (edited)
  On 7/13/2022 at 6:39 PM, Gausus said:

I have 2 H96max+ RK3328 โˆ• 4GB  tvboxes.

 

Armbian 22.08 - Debian Bullseye minimal - mainline kernel 5.18.10

 

To boot from sdcard when Android on internal storage.

1. Flash Armbian on sdcard

2. Download Multitool.img 

3. Mount multitool.img on linuxpc or flash to another sdcard.

4. Copy  trustos.img and uboot.img from bsp folder to a folder on linuxpc,

5 . DD trustos.img and uboot.img to sdcard Armbian from linuxpc

 

sudo dd if=uboot.img of=/dev/SDCARD seek=16384 conv=fsync
sudo dd if=trustos.img of=/dev/SDCARD seek=24576 conv=fsync
Expand  

Could not get this to work with neither of the first post images.

X88 Pro 10 with in an tf card set up like this it does not do anything at all. How did you arrive at those seek values?

Edited by Aapo Tahkola
Posted

Hi! Thanks for images at first.
I'm trying to launch docker on your image but get problems with cgroup.
dockerd --debug output:

  Reveal hidden contents

 

cgroupfs-mount:

  Reveal hidden contents

 

I see this row in dmesg which looks suspectable for me: Unknown kernel command line parameters "ubootpart=534ffe7a-01 cgroup_enable=memory cgroup_memory=1", will be passed to user space.

Full dmesg:

  Reveal hidden contents

 

I tried 22.05 version of the image first and then uninstalled docker and updated to 22.08 through installing packages from "upgrade" folder. After installation I still have this issue.
Can somebody help, please?

Posted (edited)
  On 7/11/2022 at 5:46 PM, JMCC said:

@jock Thanks for the info. On a side note, I found a small bug: when making the emmc backup, if the resulting file is bigger than 4Gb it will just stop there (because of the FAT size limit) and you will get a broken backup.

 

Probably could be solved by splitting the backup, for example along these lines:

# Split backup in 2Gb parts, with two-character suffixes
dd if=/dev/mmcblk1 | gzip -c | split -b 2000m - tvbox-backup.img.gz.

# Restore the backup
cat tvbox-backup.img.gz.* | gzip -dc | dd of=/dev/mmcblk1

 

Expand  

Armbian_22.08.0-trunk_Rk3318-box_jammy_edge_5.18.6_xfce_desktop.img is hair over 4GB so trying to flash that also fails. Seems like the files sizes are going to be a problem.

I flashed Armbian_22.08.0-trunk_Rk3318-box_bullseye_edge_5.18.10_minimal.img to my X88 pro 10 with 4 gb ram and 32gb emmc after first erasing emmc(is this ok?) and I cannot get a beep out of it anymore. Soldered uart but I cannot seem to find a working baud rate. Tried every commonly used rate. It just shows as short beep of garbage with picocom after powering up. What should I do now?

 

I got sent couple weeks old new firmware for this box if anyone is interested. The new fw has working 5 ghz wifi on the upper band and connecting bluetooth to speakers works unlike before. Youtube app crashed once on it so pretty sure the clocks are too high though.

 

https://drive.google.com/u/0/uc?id=17sG7TnQbw3YH2XdHnwHDbgyzMRubwZtG&export=download

https://drive.google.com/drive/folders/1y9rBkpD_FenjvAwmiehnRL8OhzTt3mwX

Edited by Aapo Tahkola
updates2
Posted
  On 7/21/2022 at 5:14 AM, Aapo Tahkola said:

Seems like the files sizes are going to be a problem.

Expand  

yes, it looks like they are becoming a real problem. multitool was early meant for rk322x devices, which have smaller eMMC and usually the whole compressed backup fits in 4gb, but rk3318 have up to 64gb eMMC and things don't work anymore.

 

Uart is 1.5Mbps, it should talk telling you what's wrong.

If it does not give you anything at all you may try to connect a USB Male-to-Male cable to the OTG Usb port of the box and to a computer and see if lsusb shows a rockchip device in maskrom mode.

Posted (edited)
  On 7/21/2022 at 2:49 PM, jock said:

yes, it looks like they are becoming a real problem. multitool was early meant for rk322x devices, which have smaller eMMC and usually the whole compressed backup fits in 4gb, but rk3318 have up to 64gb eMMC and things don't work anymore.

 

Uart is 1.5Mbps, it should talk telling you what's wrong.

If it does not give you anything at all you may try to connect a USB Male-to-Male cable to the OTG Usb port of the box and to a computer and see if lsusb shows a rockchip device in maskrom mode.

Expand  

None of these picocom supported speeds make sense out of the output:

576000, 921600, 1000000, 1152000, 1500000, 2000000, 2500000, 3000000, 3500000, 4000000

I found out that the factory flash tool does not work anymore even when pressing the hidden button.

I have been trying to get https://github.com/pico-coder/sigrok-pico work on rpi pico or rpi pico w but there is a bug somewhere so I cannot used it yet. I did have not much trouble compiling it under linux. Should I get that to work, it should be fairly easy to figure out what is going on with the uart. There is an open issue on sigrok-pico about it.

 

So I did a backup restore and factory tool started working again. So I used factory tool again and I am basically back at day one. I do find it a bit strange that the factory tool did not work anymore after flashing. Cannot really think of anything I could do at this point though.

 

 

I think 5.15 kernel has writable ntfs support. I think ntfs-3g with write support has been stable for a long time by now. I cannot say I like the split file approach. Just to be clear, I think there is a good chance that the incomplete backups still manage to boot it is just that the backup being incomplete almost certainly breaks something.

Wifi is sp6330 on this board, ddr3 are samsung k4b4g0446c

 

Edited by Aapo Tahkola
update
Posted (edited)

Hi.
I bricked my plate and want to unbrick it. But can't find clock pin.
Here is the emmc chip and it's back. Can somebody tell what should I short here to erase emmc?
Thanks in advance.

  Reveal hidden contents

 

P.S. What should I do after going into maskrom mode? Should I attach box to a computer with usb? Should I plug usb after enabling maskrom or before?

Edited by DmitryS
Posted

@DmitryS The MCC is U2300 and on the underside of the PCB you have 2 test points TP2300 and TP2301 (GND).

You can trying shutting them with one high ohm resistor for being safe (or only some metal if not playing safe and can damage the board) and putting in one USB cable from your PC in the OTG port and see if the SOC is booting in masc rom more.

 

Some of the hardware specialist here is knowing more but im 95% sure its the masc rom TPs on your board but no one can grantee it before have testing it and its all on your own risk !!

 

Its also looks you is having one unpopulated pin row for console that can being good if need doing more debug (after getting your board booting OK).

Posted (edited)
  Quote

โ€ข Mainline u-boot

Expand  

 

 

Please write instructions on how you make the mainline u-boot. I collect according to thisinstructions and see:

U-Boot TPL 2022.07-rc6-00006-g2d2c61ff04 (Jul 23 2022 - 00:45:42)
DDR3, 333MHz
BW=32 Col=11 Bk=8 CS0 Row=16 CS=1 Die BW=16 Size=4096MB
Trying to boot from BOOTROM
Returning to boot ROM...

<debug_uart>
<debug_uart>

U-Boot SPL 2022.07-rc6-00006-g2d2c61ff04 (Jul 23 2022 - 00:45:42 +0300)
Trying to boot from MMC2
mmc_load_image_raw_sector: mmc block read error
Trying to boot from MMC1
mmc_load_image_raw_sector: mmc block read error
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###

 

Edited by buratino
Posted
  On 7/23/2022 at 5:31 AM, MattWestB said:

@DmitryS The MCC is U2300 and on the underside of the PCB you have 2 test points TP2300 and TP2301 (GND).

You can trying shutting them with one high ohm resistor for being safe (or only some metal if not playing safe and can damage the board) and putting in one USB cable from your PC in the OTG port and see if the SOC is booting in masc rom more.

 

Some of the hardware specialist here is knowing more but im 95% sure its the masc rom TPs on your board but no one can grantee it before have testing it and its all on your own risk !!

 

Its also looks you is having one unpopulated pin row for console that can being good if need doing more debug (after getting your board booting OK).

Expand  

Hi! Sorry for the long reply and thanks!
I shortened TP2300 and TP2301 before plugging cable and, as said in the instruction, blue led started blinking but I don't see any new device in lsusb on the host computer.

Posted
  On 7/24/2022 at 9:57 AM, DmitryS said:

Hi! Sorry for the long reply and thanks!
I shortened TP2300 and TP2301 before plugging cable and, as said in the instruction, blue led started blinking but I don't see any new device in lsusb on the host computer.

Expand  

Multitool and armbian pristine images are configured to set the led to blink continously (it is useful to understand if the kernel is alive or freezed).

Maybe you left an sdcard in the sd card slot with multitool/armbian image on it? Shorting the eMMC clock pin just makes the eMMC undetectable by SoC, so the SoC will continue with other boot options (ie: sdcard), and will go in maskrom mode only if there is not other valid boot option.

Posted
  On 7/23/2022 at 10:06 AM, buratino said:

Please write instructions on how you make the mainline u-boot. I collect according to thisinstructions and see:

Expand  

Armbian source code is there for your interest.

Posted

I would like to ask, is it possible to set a higher transmitter power for bluetooth? Now it can only transmit audio at a distance of 60 cm from the box.

Thanks.

Posted (edited)
  On 7/11/2022 at 5:16 PM, Seth said:

 

Expand  

Hello again.

manual upgrade from 5.15 to 5.18 kernel and dtb works flawlessly. everything works except hdmi. im currently running my h96 max box with board version rk3318_v1.4. my procedure was install armbian with kernel 5.15 using multitool and sd card while plugged in to an hdmi monitor/tv since multitool and 5.15 kernel works with hdmi. after configuring with rk3318-config, i plug it in to lan and continue running the box headless, then i manually upgrade to 5.18 kernel and dtb. config was 1.1GHz, ddr and emmc is option 1 (typical speeds), led conf i used is led-conf1 (YK led conf i think). seems to work fine and stable apart from the hdmi. i have attached dmesg for 5.15 and 5.18 logs if anyone can spot differences.

dmesg-5.15-kernel.logFetching info... dmesg-5.18-kernel.logFetching info...

Edited by Seth
Posted
  On 7/24/2022 at 10:50 AM, jock said:

Multitool and armbian pristine images are configured to set the led to blink continously (it is useful to understand if the kernel is alive or freezed).

Maybe you left an sdcard in the sd card slot with multitool/armbian image on it? Shorting the eMMC clock pin just makes the eMMC undetectable by SoC, so the SoC will continue with other boot options (ie: sdcard), and will go in maskrom mode only if there is not other valid boot option.

Expand  

Thanks for the explanation. I finally unbricked it. What I figured out is that I should put a sd-card. I put it into the board, shortened contacts which MattWestB helped me to find and it booted into multitool where I choose to burn another image and now it boots into it from emmc! Thank you guys!

Posted
  On 7/24/2022 at 8:18 PM, paradigman said:

I would like to ask, is it possible to set a higher transmitter power for bluetooth? Now it can only transmit audio at a distance of 60 cm from the box.

Thanks.

Expand  

don't know, all my bluetooth chips (AP6330, AP6334 and rtl8703bs) never had distance issues and never had to tweak anything, can stream audio 3 meters away without issues.

Posted

@Seth the HDMI disappearing is quite disappointing, since I did not tweak that part in 5.18.

 

Anyway this looks very suspicious to me:

[    2.099836] rockchip-drm display-subsystem: [drm] Cannot find any crtc or sizes
[    2.100004] rockchip-drm display-subsystem: [drm] Cannot find any crtc or sizes

 and maybe is somehow related to EDID or alike

Posted (edited)
  On 7/11/2022 at 11:10 PM, JMCC said:

Sorry, anybody has a stock-android flash backup for X88 Pro 10, made with jock's Multitool? I have been trying to use the official Rockchip tool to flash the firmware, but no luck, these devices are so crappy...

 

(More info: I made a backup, but it is corrupted due to the 4Gb bug)

Expand  

 

@JMCC

I think I have another one of these X88 Pro 10 TV box lying around (actually I managed to acquire quite a few RK3318/RK3328 TV boxes at a bargain sale store).

It's of the model 4GB RAM + 128 EMMC storage.    Do you still want it?

 

UPDATE:  It looks @Aapo Tahkola already posted a new firmware for X88 Pro 10 TV box.  Would that help you?

 

Edited by Willy Moto
Update with new firmware version discussion
Posted (edited)

Hi. It's me again. I want to know: is there any way to install opencl on rk3328 with your image? I tried to install libs from here and after that I see these files in my system:

/opt/libmali-gbm/libOpenCL.so
/usr/lib/arm-linux-gnueabihf/libOpenCL.so
/usr/lib/aarch64-linux-gnu/libOpenCL.so

 

But clpeak fails to build with error:

No rule to make target ยซ/usr/lib/aarch64-linux-gnu/libOpenCL.soยป.

 

UPD: I reinstalled packages from the link and did a little clearing in the system and now clpeak launches and says:

clGetPlatformIDs (-1001)
no platforms found

Edited by DmitryS
Posted

@DmitryS There is no opensource OpenCL driver in mesa, what you want to use is the closed source binary.

The closed source binary requires the closed source drivers; it can be installed and probably brought into working state, but it is a real PITA  since it requires the proprietary mali kernel driver first, then the closed source blobs and finally the closed source OpenCL driver. I hope I scared you enough, because that way is very scary by itself.

 

Just a side consideration: people, in general, should be very thankful for opensource drivers that make things work out of the box  and should heavily blame companies that put obstacles - like ARM does.

Posted
  On 7/27/2022 at 12:52 PM, DmitryS said:

@jock that's sad. Thanks for the answer.

Expand  

You're welcome. I hope someone will try to bring an open Vulkan driver over Mali hardware, that would be very nice when will happen.

Posted
  On 7/28/2022 at 5:46 AM, usual user said:

I think I have to disappoint you, see here.

Expand  

Well I didn't expect a fully conformant Vulkan driver since hardware is not thought for such API.

I expected something more like this https://github.com/Yours3lf/rpi-vk-driver as long as Videocore IV is way older and limited than Midgard or Bifrost (which, according to Alyssa, has been sawed away from PanVK as well... ๐Ÿ˜• )

Posted (edited)
  On 7/19/2022 at 1:54 PM, Aapo Tahkola said:

Could not get this to work with neither of the first post images.

X88 Pro 10 with in an tf card set up like this it does not do anything at all. How did you arrive at those seek values?

Expand  

 

Found info from this post:

 

Some general info her on u-boot for RK. https://u-boot.readthedocs.io/en/latest/board/rockchip/rockchip.html

 

1. Can you boot from Multitool.img ? , IF no then its will not be possible to boot Armbian from sdcard.

2. If you can , burn Armbian 22.08 - Debian image found inn first post  to sdcard.

3. Burn Multitool.img to another sdcard or mount image on Linuxpc

 

Manuel mount multitool.img

From terminal.

 

cd $HOME/Downloads/

 

# find first unused device  , /dev/loop(24)

losetup -f

 

# Mount img on /dev/loop24

 

sudo losetup -P /dev/loop24 multitool.img   

 

# Open file-browser  MULTITOOL/bsp/

# copy uboot.img and trustos.img to $HOME/Download Linuxpc

# Insert sdcard to linuxpc and find dev of sdcard / often last sdX

 

lsblk -f  

 

# My sdcard is assigned /dev/sdf

 

# DD uboot and trust IMG to sdcard armbian

# Replace /dev/SDCARD  to your dev for sdcard like sdf


 

sudo dd if=uboot.img of=/dev/SDCARD seek=16384 conv=fsync 
sudo dd if=trustos.img of=/dev/SDCARD seek=24576 conv=fsync

 

If this not work you can copy the generic DTB rk3318-box.dtb form multitool.img to sdcard.

You find generic DTB on root /  multitool.

Copy this to /boot/dtb/rockchip SDCARD to overwrite DTB on Armbian image.

 

Or burn older Armbian img to test if they boots form sdcard when Android on internal storage.

 

Happy booting!!

 

 

Edited by Gausus

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.

ร—
ร—
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines