jock
-
Posts
2159 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by jock
-
-
12 hours ago, MMarcio said:
My first question concerns the deletion of the nand memory in order to allow the boot of linux, I do not understand the procedure to be performed, I have all the equipment and I use Ubuntu 19.10 on my laptop to be able to flash (I only understood that there is need linux to make the various flashes)
The procedure is described in a bunch of simple steps in the first page of the thread.
All you need is just a male-to-male USB cable and rkdeveloptool binary.
Linux is not absolutely needed (rkdeveloptool is available also for Windows, but don't ask me where) but is really really suggested.
12 hours ago, MMarcio said:Has anyone created a video guide about it?
AFAIK, nope
12 hours ago, MMarcio said:My second question concerns the jumper on the nand, is it used to send the card in "debug" mode in order to be detected by my pc?
It used to bypass the eMMC/NAND (your board has an eMMC), in fact shorting that ping you are clock gating the eMMC/NAND device, so the processor thinks there is no eMMC/NAND device at all and tries to boot from the external microsd card. If also there isn't any microsd card, the processor puts itself in MASKROM mode, which is a sort of maintenance mode accessible from a PC connected to the OTG USB port using rkdeveloptool.
If you can't write on the forum, write me or @fabiobassa in private.
-
18 minutes ago, nokirunner said:
probably indendevi with the addition of ul, otherwise it tells me that illegal operation ...
Sorry I missed the commands.
Now I fixed the post
-
Try these instructions, they worked perfectly well for me on two different boards, including the clone of yours.
I suppose your eMMC is empty, if not erase it the way you prefer.
- Download this binary: rk322x_loader.bin in your rkdeveloptool directory
- Detach all the cables from the box
- Attach the male-to-male USB cable to the USB port near the HDMI
- Attach the other end of the USB cable to an USB2 port of your computer. Now with lsusb you should see 2206:3206 device listed.
- run sudo ./rkdeveloptool db rk322x_loader.bin, it should finish in less than 5 seconds
- run sudo ./rkdeveloptool wl 0x0 image.img, where image.img is one of your preference taken from the first page of this thread (others will just not work).
- Wait until done, then detach the USB cable and you're done
This works perfectly for me
-
Both rk3288 and rk322x now works fine with kernels (5.5 for rk3288 and 5.6 for rk322x) compiled without VDSO.
Chrony still is not able to start, so it is not related to this one: uninstalling it via apt, systemd automatically resorted to systemd-timesyncd which immediately synced with remote NTP server.
-
I made a strace of date utility and got this:
Spoilerpaolo@xt-q8l-v10:~$ strace date
execve("/usr/bin/date", ["date"], 0xbef816a0 /* 24 vars */) = 0
brk(NULL) = 0x1b8f000
mmap2(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb6f50000
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=58027, ...}) = 0
mmap2(NULL, 58027, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb6f1a000
close(3) = 0
openat(AT_FDCWD, "/lib/arm-linux-gnueabihf/libc.so.6", O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 3
read(3, "\177ELF\1\1\1\3\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\331\252\1\0004\0\0\0"..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=972500, ...}) = 0
mmap2(NULL, 1038540, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xb6e1c000
mprotect(0xb6f04000, 65536, PROT_NONE) = 0
mmap2(0xb6f14000, 16384, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xe8000) = 0xb6f14000
mmap2(0xb6f18000, 6348, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb6f18000
close(3) = 0
set_tls(0xb6f50e10) = 0
mprotect(0xb6f14000, 8192, PROT_READ) = 0
mprotect(0x4db000, 4096, PROT_READ) = 0
mprotect(0xb6f52000, 4096, PROT_READ) = 0
munmap(0xb6f1a000, 58027) = 0
brk(NULL) = 0x1b8f000
brk(0x1bb0000) = 0x1bb0000
openat(AT_FDCWD, "/usr/lib/locale/locale-archive", O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=3035952, ...}) = 0
mmap2(NULL, 2097152, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb6c1c000
mmap2(NULL, 2596864, PROT_READ, MAP_PRIVATE, 3, 0x6c000) = 0xb69a2000
close(3) = 0
syscall_0x193(0, 0xbeac5438, 0xbeac5438, 0xfe354, 0, 0xbeac5438) = 0
openat(AT_FDCWD, "/etc/localtime", O_RDONLY|O_CLOEXEC) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=118, ...}) = 0
fstat64(3, {st_mode=S_IFREG|0644, st_size=118, ...}) = 0
read(3, "TZif2\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0\1\0\0\0\0"..., 4096) = 118
_llseek(3, -62, [56], SEEK_CUR) = 0
read(3, "TZif2\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0\1\0\0\0\0"..., 4096) = 62
close(3) = 0
fstat64(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(0x88, 0), ...}) = 0
write(1, "Tue 14 Apr 2020 08:08:29 PM UTC\n", 32Tue 14 Apr 2020 08:08:29 PM UTC
) = 32
close(1) = 0
close(2) = 0
exit_group(0) = ?
+++ exited with 0 +++Now I don't see any clock_gettime, but there is a syscall_0x193, of which I found some references here. I'm compiling a kernel with vDSO disabled just to see what happens.
It could be it is affecting 32 bit arm (rk322x and rk3288), but not 64 bit arm (@Werner Opi1+)
-
-
Possibly, I just build for rk3288 and kernel 5.5.17: I don't have the system time jumping around, but still many systemd services have issues, don't start or keep failing. e2scrub_all and fstrim seem to be particularly affected.
Running systemctl alone to show the services often instantly fails with "Failed to read server status: Connection timed out".
edit: I correct myself, system time is jumping around also on rk3288
-
-
4 hours ago, nokirunner said:
don't tell me ... are you italian too?
Yes sir!
It looks like this is the cove of the quarantined people, never seen so many italians on the forum
3 hours ago, nokirunner said:guys, you have not commented on this, can these driver sources be useful?
Good catch, it looks very promising. I did not see that post before. but I will try to compile as soon as I can!
1 hour ago, MMarcio said:I know it will be annoying but the guide to clear the internal memory of the box is not clear to me, could someone make me understand the procedure better?
Sure, just ask about anything!
-
Hmm guys, I'd like to say that you should stay away from Ubuntu Focal with mainline kernel images for now. This applies to people who downloaded the image in the past, because at the moment I didn't propose one in the first page.
There is a very strange issue with the system time that makes the image not work reliably. I opened a new thread about because at the moment I'm clueless about.
-
I'm experience a really weird problem on a very experimental setup: the system is an Armbian build for an unsupported board (Rockchip RK322x) and Ubuntu Focal 20.04 with mainline kernel 5.6.4.
The system has issues to boot when enters into systemd: it is slow but all of sudden it goes farther. Many different systemd services are complaining, expecially the journal and the chrony NTP client. Finally I found that the root of the problems is the system time which is abruptly moving back and forth even by months.
Subsequent calls to date may report 20 June, then 4 March, then 18 August and so on...
The kernel log is fine and, most of all, the very same kernel works perfectly with Debian Buster 10 and Ubuntu Eoan 19.10.
Also Ubuntu Focal 20.04 works fine using the legacy rockchip 4.4.194 kernel.
I also booted from a clean Ubuntu Eoan 19.10 and then upgraded to Focal via apt; the problem manifested the same way, but I got some logging errors telling me that an assertion failed on clock_gettime() system call, which does not returned 0 as expected.
All the installations were Armbian Minimal, so no GUI or advanced services whatsoever.
Any ideas?
-
@Maker39 The problem with power-on with remote is that the box is... powered off!
The original firmware does never really shut the box off, but keep it in suspend state in u-boot, u-boot "listens" and then is able to react to remote power key and trigger the bootstrap.
When you shut down in armbian or libreelec, the box is really powered down, so you need to do a full power-cycle. I didn't investigate too much into this problem, but this is a very common problem on most boards on different platforms when you switch away from original firmware.
-
8 hours ago, nokirunner said:
non si era capito?
You disguised very well
I would have said you were American, or Mexican
5 hours ago, nokirunner said:as soon as i installed the full firmware package from armbian comfig, the system became noticeably more responsive, almost reaching the capabilities of a real desktop, can anyone explain this to me?
Nope didn't experience anything like that, but I will definitely check. Which image are you using?
In the meantime, could you run openssl speed -multi 4 rsa and post the summary results here? It's just an openssl benchmark to compare performances.
-
12 minutes ago, nokirunner said:
as firmware there are two, but as kernel object I have found only one ...
so if math is not an opinion I have good hopesI'm getting a bit suspicious about this ssv6x5x driver, which does not appear anywhere in rockchip source code. Maybe our ssv6051 is a stripped down or older release, or just an incompatible driver with 62xx series, despite it is heavily based on
-
1 hour ago, nokirunner said:
@fabiobassa
trust me, with woodoo, everything has happened so far because this wifi must now start working 😂
edit:
just to get you noticed, I have not found any ssv6051.ko file ... only ssv6x5x.ko
could this be a good sign?My guess is that ssv6051p and ssv6256p share the same driver. Looking into the code I see no reference about ssv6x5x file name at all.
This is the dmesg messages related to ssv6051 module with ssv6256p firmware:
Spoiler[ 45.556757] generic_wifi_init_module
[ 45.834624]
*** sta_cfg_set, /etc/firmware/ssv6051-wifi.cfg ***[ 45.842138] ssv6xxx_sdio_init
[ 45.843465] =======================================
[ 45.843528] == RUN SDIO ==
[ 45.843539] =======================================
[ 45.843555] ssv6xxx_set_sdio_clk:set sdio clk 25000000Hz
[ 45.843659] mmc_host mmc1: Bus speed (slot 0) = 25000000Hz (slot req 25000000Hz, actual 25000000HZ div = 0)
[ 45.863765] SSV6XXX_SDIO mmc1:0001:1: vendor = 0x3030 device = 0x3030
[ 45.873969] ssv6xxx_sdio_power_on
[ 45.886730] SSV6XXX_SDIO mmc1:0001:1: dataIOPort 0x10000 regIOPort 0x10020
[ 45.887390] ssv6xxx_dev_probe(): ssv6200 device found !
[ 45.888102] ssv6xxx_sdio_irq_disable
[ 45.888633] Read open File fail[/data/wifimac]!!!!
[ 45.888721] Write open File fail!!!![/data/wifimac]
[ 45.888735] MAC address from Software MAC mode[2]
[ 45.888741] EFUSE configuration
[ 45.888748] Read efuse chip identity[00000000]
[ 45.888754] r_calbration_result- 0
[ 45.888759] sar_result- 0
[ 45.888768] crystal_frequency_offset- 0
[ 45.888774] tx_power_index_1- 0
[ 45.888783] tx_power_index_2- 0
[ 45.888801] MAC address - 00:00:00:00:00:00
[ 45.889458] Registering Vendor80211
[ 45.889496] Register SSV cfg80211 vendor cmd(0x67) interface
[ 45.889730] [MT-ENCRYPT]: create kthread ecf95540 for CPU 0, ret = 0
[ 45.889817] SSV WLAN driver ssv6200: Crypto task 1304 running with priority 120.
[ 45.889940] [MT-ENCRYPT]: create kthread ecf926c0 for CPU 1, ret = 0
[ 45.890132] [MT-ENCRYPT]: create kthread ecf91f00 for CPU 2, ret = 0
[ 45.890195] SSV WLAN driver ssv6200: Crypto task 1306 running with priority 120.
[ 45.890309] [MT-ENCRYPT]: create kthread ecf93e00 for CPU 3, ret = 0
[ 45.890365] SSV WLAN driver ssv6200: Crypto task 1307 running with priority 120.
[ 45.891566] SSV WLAN driver ssv6200: Crypto task 1305 running with priority 120.
[ 45.892313] Pre-load cipher
[ 45.892345] SSV6XXX TX Task started.
[ 45.892563] flash_file /tmp/flash.bin not found, disable sar
[ 45.892591] SSV6051Q setting
[ 45.892605] SSV6XXX_IQK_CFG_XTAL_24M
[ 45.892618] SSV6051Q setting [0x5B606C72]
[ 45.892625] TX power setting 0x5b606c72
[ 45.892635] Volt regulator LDO
[ 45.892766] SSV6XXX RX Task started.
[ 45.895789] reset PLL
[ 45.914280] @@@@@@@@@@@@
[ 45.914320] SDIO issue -- please check 0xCE01008C 00000000!!
[ 45.914327] It shouble be 0xEAAAAAAA!!
[ 45.914336] @@@@@@@@@@@@
[ 45.937648] calibation fail:[1]
[ 45.959777] calibation fail:[2]
[ 45.981931] calibation fail:[3]
[ 46.004182] calibation fail:[4]
[ 46.026301] calibation fail:[5]
[ 46.048781] calibation fail:[6]
[ 46.071022] calibation fail:[7]
[ 46.093537] calibation fail:[8]
[ 46.115729] calibation fail:[9]
[ 46.137833] calibation fail:[10]
[ 46.159976] calibation fail:[11]
[ 46.182168] calibation fail:[12]
[ 46.204509] calibation fail:[13]
[ 46.226641] calibation fail:[14]
[ 46.248736] calibation fail:[15]
[ 46.270894] calibation fail:[16]
[ 46.293056] calibation fail:[17]
[ 46.315271] calibation fail:[18]
[ 46.337411] calibation fail:[19]
[ 46.359522] calibation fail:[20]
[ 46.381625] calibation fail:[21]
[ 46.403774] calibation fail:[22]
[ 46.425883] calibation fail:[23]
[ 46.448203] calibation fail:[24]
[ 46.470381] calibation fail:[25]
[ 46.492836] calibation fail:[26]
[ 46.514988] calibation fail:[27]
[ 46.537210] calibation fail:[28]
[ 46.559383] calibation fail:[29]
[ 46.581515] calibation fail:[30]
[ 46.603728] calibation fail:[31]
[ 46.625870] calibation fail:[32]
[ 46.648113] calibation fail:[33]
[ 46.670330] calibation fail:[34]
[ 46.692797] calibation fail:[35]
[ 46.715004] calibation fail:[36]
[ 46.737205] calibation fail:[37]
[ 46.759373] calibation fail:[38]
[ 46.781603] calibation fail:[39]
[ 46.803675] calibation fail:[40]
[ 46.825797] calibation fail:[41]
[ 46.847990] calibation fail:[42]
[ 46.870248] calibation fail:[43]
[ 46.892723] calibation fail:[44]
[ 46.914889] calibation fail:[45]
[ 46.937041] calibation fail:[46]
[ 46.959255] calibation fail:[47]
[ 46.981358] calibation fail:[48]
[ 47.003487] calibation fail:[49]
[ 47.025574] calibation fail:[50]
[ 47.047707] calibation fail:[51]
[ 47.069863] calibation fail:[52]
[ 47.092331] calibation fail:[53]
[ 47.114575] calibation fail:[54]
[ 47.136721] calibation fail:[55]
[ 47.158783] calibation fail:[56]
[ 47.180975] calibation fail:[57]
[ 47.203144] calibation fail:[58]
[ 47.225262] calibation fail:[59]
[ 47.247367] calibation fail:[60]
[ 47.269600] calibation fail:[61]
[ 47.291714] calibation fail:[62]
[ 47.313747] calibation fail:[63]
[ 47.335921] calibation fail:[64]
[ 47.358070] calibation fail:[65]
[ 47.380291] calibation fail:[66]
[ 47.402418] calibation fail:[67]
[ 47.424802] calibation fail:[68]
[ 47.446886] calibation fail:[69]
[ 47.469056] calibation fail:[70]
[ 47.491270] calibation fail:[71]
[ 47.513351] calibation fail:[72]
[ 47.535462] calibation fail:[73]
[ 47.557566] calibation fail:[74]
[ 47.579698] calibation fail:[75]
[ 47.601857] calibation fail:[76]
[ 47.624048] calibation fail:[77]
[ 47.646174] calibation fail:[78]
[ 47.668596] calibation fail:[79]
[ 47.690722] calibation fail:[80]
[ 47.712856] calibation fail:[81]
[ 47.734973] calibation fail:[82]
[ 47.757146] calibation fail:[83]
[ 47.779344] calibation fail:[84]
[ 47.801606] calibation fail:[85]
[ 47.823737] calibation fail:[86]
[ 47.845878] calibation fail:[87]
[ 47.868059] calibation fail:[88]
[ 47.890308] calibation fail:[89]
[ 47.912775] calibation fail:[90]
[ 47.934958] calibation fail:[91]
[ 47.957122] calibation fail:[92]
[ 47.979265] calibation fail:[93]
[ 48.001351] calibation fail:[94]
[ 48.023461] calibation fail:[95]
[ 48.045546] calibation fail:[96]
[ 48.067706] calibation fail:[97]
[ 48.090197] calibation fail:[98]
[ 48.112805] calibation fail:[99]
[ 48.135072] calibation fail:[100]
[ 48.143782] ieee80211 phy0: Selected rate control algorithm 'ssv6xxx_rate_control'
[ 48.175081] ieee80211 phy0: SSV6200 of South Silicon Valley
[ 48.338231] IPv6: ADDRCONF(NETDEV_UP): p2p0: link is not ready
[ 48.339953] SVN version 16529
[ 48.339988] SVN ROOT URL http://192.168.15.30/svn/software/project/release/android/box/rk3x28/6051.Q0.1009.21.400401/ssv6xxx
[ 48.339999] COMPILER HOST icomm-buildserver-T320
[ 48.340009] COMPILER DATE 12-08-2017-10:34:54
[ 48.340016] COMPILER OS linux
[ 48.340025] COMPILER OS ARCH x86_64-linux-gnu-thread-multi
[ 48.340742] CHIP TAG: 0
[ 48.341639] CHIP ID: SSV6006C0
[ 48.355863] 0x800e0000
[ 48.422300] ERROR!!Please check interface!
[ 48.422359] [0xca000200]: 0x0c000000!=0x00000000
[ 48.422369] SOS!SOS!
[ 48.422380] Initialize ssv6200 mac fail!!
[ 48.455241] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 48.455753] SVN version 16529
[ 48.455782] SVN ROOT URL http://192.168.15.30/svn/software/project/release/android/box/rk3x28/6051.Q0.1009.21.400401/ssv6xxx
[ 48.455792] COMPILER HOST icomm-buildserver-T320
[ 48.455798] COMPILER DATE 12-08-2017-10:34:54
[ 48.455805] COMPILER OS linux
[ 48.455812] COMPILER OS ARCH x86_64-linux-gnu-thread-multi
[ 48.456174] CHIP TAG: 0
[ 48.456528] CHIP ID: SSV6006C0
[ 48.461840] 0x800e0000
[ 48.501769] ERROR!!Please check interface!
[ 48.501814] [0xca000200]: 0x0c000000!=0x00000000
[ 48.501824] SOS!SOS!
[ 48.501834] Initialize ssv6200 mac fail!!
[ 48.536594] SVN version 16529
[ 48.536637] SVN ROOT URL http://192.168.15.30/svn/software/project/release/android/box/rk3x28/6051.Q0.1009.21.400401/ssv6xxx
[ 48.536646] COMPILER HOST icomm-buildserver-T320
[ 48.536652] COMPILER DATE 12-08-2017-10:34:54
[ 48.536658] COMPILER OS linux
[ 48.536665] COMPILER OS ARCH x86_64-linux-gnu-thread-multi
[ 48.536979] CHIP TAG: 0
[ 48.537302] CHIP ID: SSV6006C0
[ 48.541859] 0x800e0000
[ 48.577247] ERROR!!Please check interface!
[ 48.577285] [0xca000200]: 0x0c000000!=0x00000000
[ 48.577292] SOS!SOS!
[ 48.577302] Initialize ssv6200 mac fail!!
[ 48.581879] SVN version 16529
[ 48.581920] SVN ROOT URL http://192.168.15.30/svn/software/project/release/android/box/rk3x28/6051.Q0.1009.21.400401/ssv6xxx
[ 48.581927] COMPILER HOST icomm-buildserver-T320
[ 48.581938] COMPILER DATE 12-08-2017-10:34:54
[ 48.581944] COMPILER OS linux
[ 48.581953] COMPILER OS ARCH x86_64-linux-gnu-thread-multi
[ 48.582281] CHIP TAG: 0
[ 48.583507] CHIP ID: SSV6006C0
[ 48.587482] 0x800e0000
[ 48.623056] ERROR!!Please check interface!
[ 48.623095] [0xca000200]: 0x0c000000!=0x00000000
[ 48.623101] SOS!SOS!
[ 48.623110] Initialize ssv6200 mac fail!!
[ 48.637869] SVN version 16529
[ 48.637916] SVN ROOT URL http://192.168.15.30/svn/software/project/release/android/box/rk3x28/6051.Q0.1009.21.400401/ssv6xxx
[ 48.637929] COMPILER HOST icomm-buildserver-T320
[ 48.637940] COMPILER DATE 12-08-2017-10:34:54
[ 48.637946] COMPILER OS linux
[ 48.637957] COMPILER OS ARCH x86_64-linux-gnu-thread-multi
[ 48.638397] CHIP TAG: 0
[ 48.639021] CHIP ID: SSV6006C0
[ 48.642206] 0x800e0000
[ 48.677275] ERROR!!Please check interface!
[ 48.677307] [0xca000200]: 0x0c000000!=0x00000000
[ 48.677316] SOS!SOS!
[ 48.677324] Initialize ssv6200 mac fail!!
[ 48.682825] SVN version 16529
[ 48.682863] SVN ROOT URL http://192.168.15.30/svn/software/project/release/android/box/rk3x28/6051.Q0.1009.21.400401/ssv6xxx
[ 48.682873] COMPILER HOST icomm-buildserver-T320
[ 48.682883] COMPILER DATE 12-08-2017-10:34:54
[ 48.682889] COMPILER OS linux
[ 48.682898] COMPILER OS ARCH x86_64-linux-gnu-thread-multi
[ 48.683218] CHIP TAG: 0
[ 48.683599] CHIP ID: SSV6006C0
[ 48.687398] 0x800e0000
[ 48.722152] ERROR!!Please check interface!
[ 48.722192] [0xca000200]: 0x0c000000!=0x00000000
[ 48.722199] SOS!SOS!
[ 48.722206] Initialize ssv6200 mac fail!!as you see, at a certain point it says something about a register not containing the expected value and then reports errors
-
@nokirunner yes, most probably it is the right firmware file, but for some reason the last time I tried it didn't work.
The driver is not very helpful in describing what is wrong, just fails with a bunch of cryptic debug messages and so.
But I guess I can give it another chance!
-
4 minutes ago, nokirunner said:
@jock have you tried to compile the latest development-builds?
if you notice there are changes that concern a week ago on the mesa openglI didn't try to compile Kodi yet, but instead I did a quick test using the packaged one from Ubuntu Focal, which was 18.6 if I remember well.
It starts, I get to the splash screen, but then it hangs the board and can't even change to another virtual terminal.
-
47 minutes ago, nokirunner said:
out of curiosity I have seen that the drm driver Lima (mali 400-450)
are in fair development,
https://cgit.freedesktop.org/drm/drm/log/?qt=grep&q=lima
and also the mesa opengl
https://gitlab.freedesktop.org/mesa/mesa/-/commits/master/src/gallium/drivers/lima
have you already tested these in developement?
if I want to do some tests, what should I do, who can help me?
I never built in cross hardwareI'm interested in lima too.
At the current moment on libreelec it works very well on different platforms (rockchip, but also amlogic, don't know about allwinner but I guess it works fine either). On my armbian builds here, i don't know the reason why, it fails both in running X11 (which can be expected), but also Kodi without the X server, which in theory is the same configuration as libreelec.
-
13 hours ago, nokirunner said:
I answer a little to everyone to simplify ..
Yes I was referring to the usb 3 of the pc,
It is a pity that there are still companies reluctant to release the open source drivers and firmware of some hardware, yet they would all benefit us, the users who would have well-functioning hardware, and the farm maintainers who would have less time and money to invest to debug and operate at best their hardware ...
stupidity take me away. 😁
my only desire to have this tvbox operating with armbian is to set up an octoprint server so that I can remotely control my 3d printer while printing, so it is essential for me that wifi works, I only have two free usb ports , and in one I want to put a webcam and the other is connected to the 3d printer ...
it is essential for me that it is always on, that consume very little energy and so on ...
Seems a pretty interesting project. Good luck for that!
Unfortunately the keep costs down, tv box makers use chips from unknown and unreliable sources, then happens that the vendor failed (at least rumors say so) leaving us with a very badly written driver. That is one of the reasons why I avoid cheap tv boxes when doing serious pet projects, a proper single-board-computer is much more suited.
As @fabiobassa said, ssv6051p driver is suitable for ssv6256p also, but for some reason it does not work.
-
1 hour ago, Maker39 said:
I , and probably @nokirunner , meant the version of USB3.0 and USB2.0 on the PC, but not the port on the board
As far as I know, there is only one OTG (on those boards that I have seen there are MOSFETs nearby) .
Yep I totally misunderstood
-
@nokirunner @Maker39 As far as I know, the only programming USB port should be the OTG port. Sometimes it is labeled on the PCB, sometimes the enclosure has the OTG label, sometimes there is nothing telling you which port is the OTG one.
For example, the Scishion Model X (the same owned by @nokirunner) I got here has 2 USB ports, none of them is labeled OTG in any form and they are both labeled as "USB" on the chassis without any number on them.
Other devices, like the MXQ Pro 4K has the OTG signature on the PCB corresponding to the USB 4 port labeled on the chassis.
So it's a bit of hit and miss, but finding first the OTG port looking at the board can avoid many headaches later
-
14 minutes ago, nokirunner said:
./rkdeveloptool ef Creating Comm Object failed! ./rkdeveloptool wl 0x0 Armbian_20.05.0-trunk_Rk322x-box_focal_legacy_4.4.194_desktop.img Write LBA quit, creating comm object failed!my suspicions are at risk of being confirmed, I think I have done some damage
what do you say or do you think it remains to do ??
in maskrom mode, before doing executing any command, you must upload the loader. rkdeveloptool db command may come in handy, you can see how to use it on the first page in the "Restore the firmware" section.
But I would say it is far easier to just boot into linux. Just plug the sdcard into and boot with the eMMC shorted. Remember to unshort as soon as you see the red led.
-
3 minutes ago, nokirunner said:
@jock
apparently I can't flash from windows with that tool, it was the tool I used to make backups, and for some reason even if it see the mask rom mode it doesn't work as it should, (I saw some demonstration videos) I'm afraid I did some hardware damage yesterday making random attempts to find the clock pin ... now I'm trying from linux with your instructions ....
from linux the first thing i noticed, is that now the usb port is seen as 2207: 320b and it is like all the other rk2329 ... while before it was seen as 2207: 0002 ... now i am crossing my fingers hoping to have more luck ...I hope you didn't damage the eMMC. It could be that the eMMC is not available because you shorted the eMMC clock pin at boot. Shorting the eMMC to ground makes it unavailable to first stage bootloader.
Keep us informed about progress.
-
@nokirunner sorry but I don't have ever used that tool so can't be of any help.
CSC Armbian for RK322x TV box boards
in Rockchip CPU Boxes
Posted
Those hardware partitions are part of the eMMC and are available to contain "alternative" boot code. I never played with them, they could in theory be exploited for some useful purposes, but AFAIK no board uses them. I think you can ignore them, on my boards they are all empty.
I don't really know what to tell you.
You may try with blkdiscard /dev/mmcblk2 that is the proper way to erase the eMMC.