Tronsmart has a Rockchip rk3368 based set-top-box [1].

I want to use it as a arm64 based workstation running openSUSE. The first steps are done and a v4.4-rc1 based kernel boots. The only thing needed right now is the crtc module, which uses some different register mappings (and hopefully nothing else).

Things to do: 1. get the kernel booted from sd-card or usb-stick 2. get a JeOS image building and booting 3. get iommu with arm64 working 4. check if the initial implementation of crtc is working 5. do some nice patches for mainline

I'm based in Barcelona, so it will be difficult to multiplex my board with others. Anyway if someone wants to help, we can find a way. (e.g. looking on the JeOS build, searching for the iommu kernel patches etc).

[1] http://www.tronsmart.com/products/tronsmart-orion-r68-pro

Looking for hackers with the skills:

arm64 jeos kernel kiwi arm

This project is part of:

Hack Week 13 Hack Week 14

Activity

  • over 8 years ago: michals liked this project.
  • over 9 years ago: gqjiang liked this project.
  • over 9 years ago: bamvor liked this project.
  • over 9 years ago: pgonin liked this project.
  • over 9 years ago: pgonin liked this project.
  • over 9 years ago: a_faerber liked this project.
  • over 9 years ago: abergmann liked this project.
  • over 9 years ago: mbrugger started this project.
  • over 9 years ago: mbrugger added keyword "arm64" to this project.
  • over 9 years ago: mbrugger added keyword "jeos" to this project.
  • over 9 years ago: mbrugger added keyword "kernel" to this project.
  • over 9 years ago: mbrugger added keyword "kiwi" to this project.
  • over 9 years ago: mbrugger added keyword "arm" to this project.
  • over 9 years ago: mbrugger originated this project.

  • Comments

    • abergmann
      over 9 years ago by abergmann | Reply

      Nice hardware. I would like to hear back from you how good the performance is with this board and if it is good enough for daily business.

    • a_faerber
      over 9 years ago by a_faerber | Reply

      I'm expecting a GeekBox during that week and might join in rk3368 hacking later.

    • bamvor
      over 9 years ago by bamvor | Reply

      I have another rk3368 STB. I am interested in how do you boot kernel in your box? Through recovery mode?

      I could share it if some one in Beijing want to play it.

      • gqjiang
        over 9 years ago by gqjiang | Reply

        Hi bamvor,

        I'd like to play with this board, how could I access it from Beijing office?

        Thanks, Guoqing

      • mbrugger
        over 9 years ago by mbrugger | Reply

        it is a bit tricky. you need to write some garbabe to the boot partition. and then you have to write your kernel to the kernel partition and the dtb to the resource partition.

    • michals
      over 8 years ago by michals | Reply

      I have a STB with a different RK chip. With the 2G ram it can be used as thin client at best. The GPU on xx68 is something really crappy IIRC so expect fbdev is your friend for graphics. It's not like the other GPUs that could be used are supported, anyway.

    Similar Projects

    early stage kdump support by mbrugger

    Project Description

    When we experience a early boot crash, we are not able to analyze the kernel dump, as user-space wasn't able to load the crash system. The idea is to make the crash system compiled into the host kernel (think of initramfs) so that we can create a kernel dump really early in the boot process.

    Goal for the Hackweeks

    1. Investigate if this is possible and the implications it would have (done in HW21)
    2. Hack up a PoC (done in HW22 and HW23)
    3. Prepare RFC series (giving it's only one week, we are entering wishful thinking territory here).

    update HW23

    • I was able to include the crash kernel into the kernel Image.
    • I'll need to find a way to load that from init/main.c:start_kernel() probably after kcsan_init()
    • I workaround for a smoke test was to hack kexec_file_load() systemcall which has two problems:
      1. My initramfs in the porduction kernel does not have a new enough kexec version, that's not a blocker but where the week ended
      2. As the crash kernel is part of init.data it will be already stale once I can call kexec_file_load() from user-space.

    The solution is probably to rewrite the POC so that the invocation can be done from init.text (that's my theory) but I'm not sure if I can reuse the kexec infrastructure in the kernel from there, which I rely on heavily.

    update HW24

    • Day1
      • rebased on v6.12 with no problems others then me breaking the config
      • setting up a new compilation and qemu/virtme env
      • getting desperate as nothing works that used to work
    • Day 2
      • getting to call the invocation of loading the early kernel from __init after kcsan_init()
    • Day 3

      • fix problem of memdup not being able to alloc so much memory... use 64K page sizes for now
      • code refactoring
      • I'm now able to load the crash kernel
      • When using virtme I can boot into the crash kernel, also it doesn't boot completely (major milestone!), crash in elfcorehdr_read_notes()
    • Day 4

      • crash systems crashes (no pun intended) in copy_old_mempage() link; will need to understand elfcorehdr...
      • call path vmcore_init() -> parse_crash_elf_headers() -> elfcorehdr_read() -> read_from_oldmem() -> copy_oldmem_page() -> copy_to_iter()
    • Day 5

      • hacking arch/arm64/kernel/crash_dump.c:copy_old_mempage() to see if crash system really starts. It does.
      • fun fact: retested with more reserved memory and with UEFI FW, host kernel crashes in init but directly starts the crash kernel, so it works (somehow) \o/
    • TODOs

      • fix elfcorehdr so that we actually can make use of all this...
      • test where in the boot __init() chain we can/should call kexec_early_dump()