*** DEPRECATED - DON'T USE *** Rockchip RK3128 Custom Firmware for Powkiddy A12/A13 & AIWO retro-consoles
License: Other
This document is available in [ en | es | it ]
i do a backup file before flash cfw, now i need to restore original firmware but i don't know how to restore process.
please help.
Describe the bug
/etc/init.d/S49alsa (stripped rootfs from /dev/rkflash0p4) fails to call alsactl and amixer.
/tmp/rootfs/usr/sbin/alsactl and /tmp/rootfs/usr/bin/amixer exist on rootfs from sdcard (/mnt/sdcard/rukafs -> /tmp/rootfs/, mounted by /etc/init.d/S50launcher)
Custom Firmware version: ruka_cfw_3.0_beta_1_20210806
Boot output:
/etc/init.d/S49alsa: line 26: alsactl: not found
/etc/init.d/S49alsa: line 26: amixer: not found
/etc/init.d/S49alsa: line 26: amixer: not found
/etc/init.d/S49alsa: line 26: amixer: not found
Load a game into OpenBOR and remap the controls. All changes seem to be lost once you exit the game and start it again from the launcher. Previous OpenBOR version (5432) used to store changes into the config file.
Original text in Spanish:
Cargas un juego de openbor remapeas los controles y cuando sales del juego y vuelves a entrar al mismo u otro vuelven a salir la configuracion de oirigen, en la version anterior de openbor, se guardaba en el archivo config, muchas gracias por vuestro trabajo y colaboracion.
Some users are reporting that OpenBOR does not work with 3.0 alpha.
The boot logo screen is not centered on the A12 rev 3.
This is a known issue with rev3 uboot and will be fixed in the next revision.
Currently HDMI auto-switching is disabled due to the HDMI audio issue ( #1 ).
Describe the bug
Compilation fails without ../external and ../kernel folders
Custom Firmware version: [e.g. v3.0 Alpha 1]
Console (please complete the following information):
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Compilation shouldn't fail and buildroot should generate a the expected rootfs
Additional context
The external and kernel modules are part of the Rockchip buildroot system, instead of being cloned directly by the makefile, the Rockchip buildroot just assumes those folders are in place.
The following modules may need to be clone inside the ../external:
Additionally, the kernel folder should contain a copy of the general linux-4.4.118 sources (https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.4.118.tar.gz) and the folder named kernel (e.g. ln -s linux-4.4.118 kernel)
Hello.
Update script ruka_install_ps5000.sh (ruka_cfw_3.0_beta_1_20210806.tgz) partition table does not match for userdata_ps5000_20210806.img partition (offset 0x00028800).
I received updated version with different LBA offset 0x0002b000 !
$ ### different partition start (userdata) from "upgrade_tool"
$ sudo ./upgrade_tool
...
Rockusb>pl
Partition Info(gpt):
NO LBA Size Name
01 0x00002000 0x00000800 uboot
02 0x00002800 0x00001000 trust
03 0x00003800 0x00004800 boot
04 0x00008000 0x00023000 rootfs
05 0x0002b000 0x0000addf userdata
$ ### different verified from boot (serial console), factory build "Jul 8 10:53:53 CST 2021" !
$ cu -l /dev/ttyUSB0 -s 115200 -f
...
U-Boot 2017.09-gf468676-dirty (Jul 08 2021 - 10:53:40 +0800)
...
[root@root:/]# echo p | fdisk /dev/rkflash0
Found valid GPT with protective MBR; using GPT
Command (m for help): Disk /dev/rkflash0: 220672 sectors, 107M
Logical sector size: 512
Disk identifier (GUID): 9c220000-0000-4e3b-8000-557800002e7b
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 220638
Number Start (sector) End (sector) Size Name
1 8192 10239 1024K uboot
2 10240 14335 2048K trust
3 14336 32767 9216K boot
4 32768 176127 70.0M rootfs
5 176128 220638 21.7M userdata
Command (m for help): [root@root:/]#
[root@root:/]# uname -a
Linux root 4.4.159 #1047 SMP Thu Jul 8 10:53:53 CST 2021 armv7l GNU/Linux
[root@root:/]# cat /etc/os-release
NAME=Buildroot
VERSION=2018.02-rc3-00808-gc9c3b18-dirty
ID=buildroot
VERSION_ID=2018.02-rc3
PRETTY_NAME="Buildroot 2018.02-rc3"
Describe the bug
No screen image with cfw installed. At boot the screen fades from white to black
Custom Firmware version:
v3.0 Alpha 1 (RUKA_a12_RevD_3.0_alpha_20210726.img.zip)
Console:
To Reproduce
Steps to reproduce the behavior:
Screenshots
Additional context
Only CFW D can be flashed correctly (A/B/C gives IDB fail and needs MASK mode)
Connecting A12 to external monitor via HDMI works.
Seems a problem with screen setting/resolution/overscan/...
HERE THE ORIGINAL FW BACKUPPED WITH androidtool_console: A12.img
since the full image stores a12 v1/2 boot image, the boot splashscreen is cropped in the v3.
a new image with v3 ofw uboot is needed to fix it
Describe the bug
The internal speaker does not turn off when headphones are plugged in.
Custom Firmware version: v3.0 Alpha 1
Console (please complete the following information):
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The internal speaker is turned off when the headphones are plugged in.
Additional context
It seems the hotplug script is missing.
I know you have stopped developtment of RUKA, i love it and it runs great on my PS5000, i am having problems getting my wifi dongle to work.
did you include any wifi drivers and if so how can i activate them, trying to learn linux to do stuff like this.
thank you for your time.
Browsing a long list continuously crashes RetroArch. The issue is related to a RetroArch memory leak. It can be avoided by using the L/R keys to jump in increments.
Não achei o arquivo para flashear, e por isso não funciona.
Custom Firmware version: [v3.0 beta 2]
Console (PS5000):
Some issues with the current defconfig:
In general, the defconfig should be a "minimal" version with just enough packages to get retroarch frontend running (for 3.0).
When a file is modified either in the sd card or in the userdata partition, changes are not always persisted.
As a workaround, forcing sync explicitly works.
It is worth exploring whether the filesystems are mounted using the sync flag and if they aren't, test whether it could solve the problem without affecting performance.
Cuando conecto la pow12v3 con hdmi con cualquier imagen (lvb o melasu) a una pantalla grande de tv funciona todo perfectamente. El problema viene cuando se conecta a una televisión pequeña, se ve perfectamente el hdmi en la televisión pequeña pero la pantalla de la pow12 se queda encendida, además no se ve nítida la imagen, se encuentra descuadrada y descolorida.
Hice una prueba quemando la imagen melasu y de primeras, en el primer arranque, funcionó todo perfecto hasta en la televisión pequeña, la pantalla de pow se quedo apagada en negro. Volví a encender la pow conectada al hdmi y ya se quedo con la pantalla de la pow encendida y en las mismas condiciones. Volví a quemar nueva imagen melasu por si acaso fuera que se corrompiese la imagen en segundo arranque y no se resolvió el problema, sigue saliendo encendida la pantalla de la pow cuando conecto hdmi a televisión pequeña.
My Powkiddy A13 keeps crashing, I flashed Ruka CFW onto it a while ago, then this problem started.
I did not use the device anymore, now I flashed batocera onto an sd card and it boots up into batocera, but I have the same crashes that started happening when I flashed Ruka.
What happens is, the device suddenly turns off, in-game or in menu. I can barely do anything with the device before it shuts down.
I have one of the later revision A13, with the second version of the motherboard.
Could this be due to overheating, what changes did Ruka do the the device that that are still persistent when I boot into Batocera?
Did any overclocking take place?
RUKA 3.0 alpha CFW
New SDL2 library changes to get OpenGL/GLES support have introduced a regression for non-GL applications like Daphne.
Assertion failure at SDL_DestroyTexture_REAL (/opt/data/a12/dev/github/rk3128-cfw/buildroot/output/build/sdl2-2.0.7/src/render/SDL_render.c:2038), triggered 1 time:
'texture && texture->magic == &texture_magic'
The issue seems to be the same as this one here:
He probado los tres distintos firmwares y ninguno funciona correctamente en mi dispositivo.
el dispositivo es un modelo a12 recién comprado en aliexpress , sin mods, no se la versión.
Os describo el comportamiento con los 3 firmwares:
con RUKA_a12_RevD_3.0_alpha_20210726.img.zip y RUKA_a12_v3_3.0_alpha_20210504.img.zip: el resultado es muy parecido:
se muestra una pantalla como esta:
y cuando vas a cargar un core me aparece un mensaje de que el directorio no existe.
para que aparezca algun core, tengo que configurar el directorio de los cores, en los settings.
una vez hecho esto, consigo cargar un core (por ejemplo picodrive) pero la imagen se ve recortada y los botones aparecen desconfigurados.(ya no puedes volver al menu de retroarch por ejemplo.)
con el RUKA_a12_v1_v2_3.0_alpha_20210504.img.zip aparece un apantalla diferente:
y ahora los cores ya cargan sin tener que configurar ningun directorio, si cargo un core, los botones están configurados correctamente, pero el problema es que la pantalla de juego aparece recortada.
HDMI audio needs to be configured in retroarch_hdmi.cfg file. It is not included in the SD image structure that was released, and it's missing in the instructions:
Lines 70 to 83 in b05b9bc
Closing condition: SD card structure is updated and documentation is updated in all the currently available languages.
Describe the bug
L3/R3 buttons don't work and cannot be mapped on retroarch, ES, or any other emulator
Custom Firmware version: 3.0 beta 1
Console (please complete the following information):
To Reproduce
Steps to reproduce the behavior:
Expected behavior
L3/R3 should be recognized
Additional context
Neither emulators or test controller applications from SDL or udev seem to recognize those two controls. The issue is not exclusive of the PS5000, it happens with other consoles (e.g. PocketGo S30)
I flashed the CFW with no errors, copied the files onto my SD card, loaded up my SD card with roms, but I can't Load Content. When I try to Load Content, I go to my SD card, select a rom, and hit Load Archive, but I am only met with a screen that says there are no available Cores to play the rom. It says Suggested Cores, but it doesn't have any cores listed. I've even tried loading a Core first - I tried cores for MAME, SNES, and Megadrive - then Loading Content after Loading the Core, but I am met with the same issue as described above. What am I doing wrong?
Also, are there any cores for Naomi (like Flycast) on this CFW? Just wondering if I should bother adding those roms to the SD card; if there's no Core for it, I won't bother, but first, I need to get the basic stuff working (MAME, SNES, Megadrive, PCEngine, etc.)
By the way, after I found out nothing was working, I successfully used the backup.img file to return the unit to its stock firmware (ugh).
Thanks for any help.
Release Ruka CFW Release 3.0 Beta 2 for PS5000
Whenever trying to enter writing e.g. renaming a playlist or applying certain file types for a playlist, when selecting a letter it places a lower case a before inputting the letter
@snam11 realized there is an extra i at the end of the retroarch:
Before flashing anything it would be safer to have a backup of the system. It would be great to have some instructions about how to create a backup from the console's firmware.
The audio is reproduced in one channel (mono) by connecting headphones
I am using the 128 gb image from the pinned messages on telegram with the 3.0 CFW release on my powkiddy A 13. Sega CD will not launch for me. It is slightly different than openbore and hyperseus do on my system. When attempting to launch a game it returnes to the previous screen.
Works well on HDMIBad resolution on powkiddy screen
Adjunsting manually didn't solve the problem
Describe the bug
There seems to be at least two different board revisions of the PS5000. Initial custom firmware released () fails to properly flash the userdata partition in some cases, resulting in a broken system (controls don't work)
Custom Firmware version: [e.g. v3.0 Alpha 1]
Console (please complete the following information):
To Reproduce
Expected behavior
Controls should respond as expected.
Additional context
The partition table of the PS5000 seems to have at least two variations. We are going to call them Rev A & B.
Rev.A Partition Table:
Partition Info(gpt):
NO LBA Size Name
01 0x00002000 0x00000800 uboot
02 0x00002800 0x00001000 trust
03 0x00003800 0x00004800 boot
04 0x00008000 0x00020800 rootfs
05 0x00028800 0x0000d5df userdata
Rev.B Partition Table
Partition Info(gpt):
NO LBA Size Name
01 0x00002000 0x00000800 uboot
02 0x00002800 0x00001000 trust
03 0x00003800 0x00004800 boot
04 0x00008000 0x00023000 rootfs
05 0x0002b000 0x0000addf userdata
As we can see, the rootfs and userdata partitions length are different, and therefore the userdata partition starts at a different offset. Once the user flashes the Rev.A CFW into a Rev.B, the userdata partition actually overwrites the end of the rootfs partition.
Background menu music or video preview music does not work.
Emulators like:
Master System (close content after play for some time)
Playstation (crash after change some configs in some games)
SNES (close content or reboot after some time playing)
GBA (reboot)
Closing content, crash ou Reboot console.
Another emulators run very well.
Several users have notified the links to the Rockchip repo are broken due to changes in the repo.
Closing condition
Links are updated in all the installation guides (en, es, it)
The documentation template is missing the license. It is needed to add the license to the template and update the existing documents accordingly.
The license we agreed to use is CC-by-SA (perhaps 3.0 unported as Wikimedia Commons or 4.0). See https://wiki.creativecommons.org/wiki/License_Versions
HDMI is currently disabled because there's an issue with audio rendering. Audio works correctly via the local speakers but it gets incorrectly encoded while routing it via HDMI.
I'd like to pimp out my PS7000, but I can't find an English guide for the PS7000 custom firmware ANYWHERE..?
Describe the bug
I have installed the Rev D firmware on my Powkiddy A13 and everything works fine so far. The only problem is, that the configuration file causes the UI to be kind of messed up. It won't fit the whole screen. It auto-detects retroarch_v3.cfg from your SD card structure zip-file from your repo with this configuration:
video_fullscreen_x = "800"
video_fullscreen_y = "480"
video_fullscreen = "true"
However, the screen resolution of the Powkiddy A13 is 1024x600. Changing the values to these dimensions and booting into the system causes the screen to turn on and off and on again before finally turning off one last time. Then it stays black. That's it. Changing these values to 800x480 again brings back the UI.
Games will also be affected by this, not only RetroArch.
Using retroarch.cfg from your zip-file which would have the correct resolution configured has the same effect.
I've also tried installing this firmware first as it was the only one labeled with "A13":
A12/A13 | A, B | RUKA 3.0 alpha CFW | RUKA_a12_v1_v2_3.0_alpha_20210504.img.zip
But after flashing the firmware the console wouldn't boot anymore and the screen just stayed black.
I'm not sure if this is a bug with the firmware or a problem on my end. Any help would be appreciated.
Custom Firmware version:
v3.0 Alpha 1
Console (please complete the following information):
To Reproduce
Steps to reproduce the behavior:
retroarch v3.cfg to retroarch_v3.cfg in settings/retroarch/retroarch_v3.cfg and set correct screen resolution to 1024x600Expected behavior
Video output that fits the screen at 1024x600 on the boot screen and the UI/games.
Screenshots
AndroidTool_Console v2.4
Pre-scanned files for viruses, seemed clean, pressed 1 on it, then typed the command you told me.
PC:
Nuc Extreme i9 99?0HK with 2070 SUPER
64GB RAM
Latest WINDOWS 10
4TB NVME BOOT
Used USB 3.0 also used USB 3.0 double male A connector to do this. Was the only double A connector I could find.
SO... When I went to flash your rom, "Prepare IDB Fail" happens. Again had to hunt down that tool as well (RKDevTool v2.86, got this one from Firefly dot com they seem to be the official seller of RAW Rockchip boards)
If you could please instruct me on how to fix it, that would be great. I saw online a lot of talks about jumping two NAND pins, but 3 sites that mentioned it, said three different pairings; 6+7, 8+9, 10+11 AND then there was one that was like "JUMP THEM ALL" WHAT? That last one I just discarded as being silly.
Thank you again.
i've followed the guide of the PS5000 and installed the CFW just fine, but i cant make it run any roms at all, the console just keep giving me the "no core availables" message when i try to run any roms (i've put the bios on the correct folder).
i've try to flash the olders releases but the results are the same.
maybe i'm too dumb and i'm letting pass something, but i would be very grateful with some help.
Hi, I heard that the later version of A13 has IPS screen and the current v3.0 Alpha 1 does not support it.
It may cause constantly crashing the system.
I don't have proof for that but just could you confirm that the new IPS screen version of A13 are not supported yet?
How do people identify the board and screen version?
Thank you.
Current version does not include 7z support in its compilation, will be fixed in the next release.
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.