radxa rock 4c plus does not boot

[fsgh42]

I have a couple of radxa rock 4c plus devices here. I bought them because the talos website lists them as compatible but they don't boot.

I used my own manifest like this (as the official ones seem to be unknown, see below):

customization:
  extraKernelArgs:
    - gfxmode=1280x1024
    - net.ifnames=0
    - siderolink.api=https://sl.example.com/?jointoken=someToken
    - talos.events.sink=[someipv6::1]:10080
    - talos.logging.kernel=tcp://[someipv6::1]:8092
  meta:
    - key: 12
      value: |-
        "machineLabels":
          "omni.example.com/cluster": "clusterName"
          "omni.example.com/env": "testing"
  systemExtensions:
    officialExtensions:
      - siderolabs/fuse3
      - siderolabs/iscsi-tools
      - siderolabs/tailscale
      - siderolabs/util-linux-tools
overlay:
  image: siderolabs/sbc-rockchip
  name: rock4cplus

I tried setting and leaving out different options, but no luck. When flashing the image to SDcard and turning on the device, the power LED lights up, but that is it. Using the official debian based image from here I was able to rule out card or hardware failure, as it boots and works just fine.

So I can only assume it is some sort of bootloader problem and I am trying to figure out how I might be able to fix that, but I am not familiar with the build process for overlays at all - so any help is welcome.

Another user reported this as broken as well (see slack) and said there is no debug output on the serial port whatsoever (which I don't happen to have the required hardware for).

btw: The image hash referenced in the docs don't seem to exist:

$ curl -L https://factory.talos.dev/image/ed7091ab924ef1406dadc4623c90f245868f03d262764ddc2c22c8a19eb37c1c/v1.9.0-alpha.0/metal-arm64.raw.xz
schematic ID "ed7091ab924ef1406dadc4623c90f245868f03d262764ddc2c22c8a19eb37c1c" not found
$ curl -L https://factory.talos.dev/image/ed7091ab924ef1406dadc4623c90f245868f03d262764ddc2c22c8a19eb37c1c/v1.8.3/metal-arm64.raw.xz
schematic ID "ed7091ab924ef1406dadc4623c90f245868f03d262764ddc2c22c8a19eb37c1c" not found

But this can be worked around by submitting a custom schema like the above.

If there is anything I can provide or try out to get this fixed, please let me know and I am happy to help.

[DamiaPoquet]

This problem will probably be fixed when U-Boot 2025.01 is released. The Rock 4C+ is unable to boot due to memory training issues that are addressed in this commit.

The same issue is referenced here. The other option is to build the overlay using the rkbin artifact with the proprietary DDR binary from Rockchip instead.

[fsgh42]

Hi @DamiaPoquet thank you so much!
I have three 4cplus devices sitting on my desk and can test your changes, if it helps.

I will leave this issue open until a version of talos is released that supports these devices, so others avoid the situation I ran into.