Rock 4C+ v1.41: Different hardware revisions

#1

Hi,

I have a couple of Rock 4C+ boards. I noticed that there are some minor differences between them:

Board 1

Board 2

So, which is the “newer” and which the “older” one?

I have a similar issue as described here and here. I’ve been using a customized Debian image based on the scripts provided here. The resulting image (with an SPL/TPL u-boot boot loader) works perfectly fine on “Board 1”. On “Board 2”, however, it fails to boot: The board is hung with the green LED constantly on. I do not even receive any output on the serial console.

Also, when booting one of the “official” images (using a u-boot miniloader) on “Board1”, I receive valid output on the serial console. However, when booting the same image from the same SD card or eMMC module on “Board 2”, only garbage is displayed (see here). I’ve experimented with different different baud rates on the receiver side – but the result is pretty much the same for all of them.

Cheers and thanks
GH

1 Like
#2

how did you make it work on board 2 ?

  • i have:
    - 2 board as board1 == work’s perfect
    - 8 board as board2 ==> that i cannot use

BR Yannick

#3

New user and I’m very noob at hardware components and hardware/OS related programming. But this is a very good post, detailed with valid question. So I’m intrigued over why nobody has been able to answer this post for 6 months.

I have some issues of my own with my Rock 4C+ boards. Mine also sais ROCK 4C PLUS V1.41, but it has SKhynix brand RAM (H9HCNNNBPUMLHR-NEE 132a). I don’t know what Q9517 and D90006 is, but those seems to be present on mine as well.

My boards seems to be similar to your board 1, and yet I’m having some issues with mine when trying to run the official Android 11 images for 4C Plus.

rock4cplus-back
rock4cplus-back.jpg1512×2016 1.96 MB
rock4cplus-front
rock4cplus-front.jpg1512×2016 1.87 MB

Rock 4C+ Android 11 stuck in headphone mode