search

retro-center / rcade_releases

Downloads and details for R-Cade software releases and updates
Other
68 stars 3 forks source link

It works with Rock Pi 4？ #9

Closed WangONC closed 2 years ago

WangONC commented 2 years ago

It works with Rock Pi 4？ I'm looking forward to it Thank you for everything！

tatujan commented 2 years ago

Also Curious about this. Tried with RockPro64 image since they use the same chip. But can't get it to boot.

retro-center commented 2 years ago

Thanks for showing support and interest! I have not yet pushed a release for this board, but now that you’ve opened this issue - I absolutely will :)

On May 22, 2022, at 1:37 AM, Batuhan @.***> wrote:

 Also Curious about this. Tried with RockPro64 image since they use the same chip. But can't get it to boot.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.

retro-center commented 2 years ago

Latest release supports RockPi4 :)

Bortus-AI commented 2 years ago

Which version of the Rock Pi 4 is supported? I have the Rock Pi 4 c+ and the image is not working. I am getting a system boot failure. I will see if I can get any logs to assist in troubleshooting

Bortus-AI commented 2 years ago

It says to check initrd.log located in the boot partition but there is no log. Any ideas? @retro-center

retro-center commented 2 years ago

@navyfighter12 R-Cade supports RockPi4B, the device tree used can be found here: https://github.com/mrfixit2001/rockchip-kernel/blob/release-4.4/arch/arm64/boot/dts/rockchip/rk3399-rockpi-4b.dts

I don't have a RockPi4 model C to test with, unfortunately. Based on Radxa's device tree, it looks like model C does have hardware differences. I don't see anything that I would initially think would cause an issue, but these differences might possibly cause it not to boot properly. You can see differences listed here: https://github.com/radxa/kernel/blob/release-4.4-rockpi4/arch/arm64/boot/dts/rockchip/rk3399-rock-pi-4c.dts

The initrd.log file would be on the boot partition. It can only be created if the system is able to properly boot the kernel and mount the partition, however. If you're not seeing a log file then it must not be getting that far in the boot process.

You could start by trying a different eMMC or SD card, or even trying to boot off a USB drive.

NeuerUser commented 1 year ago

I have a Rock Pi 4A with 2GB RAM. I gave the latest release file (1.0.7) a try. It started successfully, showed a screen with an arcade cabinet and several activities (e.g. "expanding filesystem" and so on) and then rebootet. After reboot the screen remained black (actually "no HDMI signal"), the blue LED flashed rapidly for some time and then stopped.

I took out the SD card and found the initrd.log file. It shows the following:

`Fri Jan 18 08:50:07 UTC 2013: Initrd script initialized... | | Fri Jan 18 08:50:07 UTC 2013: Detected identified boot device with: /dev/mmcblk0p1, trying to mount... | | Fri Jan 18 08:50:07 UTC 2013: Boot partition successfully located and mounted

Fri Jan 18 08:50:07 UTC 2013: Creating in-memory filesystem (tmpfs)...

Fri Jan 18 08:50:07 UTC 2013: Initializing the rootfs - mounting as writeable...

Fri Jan 18 08:50:07 UTC 2013: Initialization complete, making rootfs readonly...

Fri Jan 18 08:50:07 UTC 2013: Mounting the rootfs overlay...

Fri Jan 18 08:50:07 UTC 2013: System successfully initialized, preparing to boot rootfs... ` That doesn't show very much, though. Apparently the boot from rootfs doesn't work, or it stops logging to initrd.log. Any idea?

NeuerUser commented 1 year ago

Addendum: After several more tries it now shows a screen. No idea, what changed, but there is a screen asking for a gamepad / controller. Now I need to read though the docs howto connect one. :-)

jocieldo commented 1 year ago

Addendum: After several more tries it now shows a screen. No idea, what changed, but there is a screen asking for a gamepad / controller. Now I need to read though the docs howto connect one. :-)

What do you did to get this screens? I also got the same log...

Fri Jan 18 08:50:08 UTC 2013: Initrd script initialized... | | Fri Jan 18 08:50:08 UTC 2013: Detected identified boot device with: /dev/mmcblk0p1, trying to mount... | | Fri Jan 18 08:50:08 UTC 2013: Boot partition successfully located and mounted Fri Jan 18 08:50:08 UTC 2013: Creating in-memory filesystem (tmpfs)... Fri Jan 18 08:50:08 UTC 2013: Initializing the rootfs - mounting as writeable... Fri Jan 18 08:50:08 UTC 2013: Initialization complete, making rootfs readonly... Fri Jan 18 08:50:08 UTC 2013: Mounting the rootfs overlay... Fri Jan 18 08:50:08 UTC 2013: System successfully initialized, preparing to boot rootfs...