ssokolow

I almost forgot to mention. The HK1 RBOX R1 has a reset button buried at the back of the 3.5mm TRS audio jack which this YouTube video demonstrates being used for some kind of DFU-esque flashing procedure using Rockchip's tools. That's all I know about it so far. EDIT: While I was waiting for these posts to be approved, I also figured out the LED: If you want the blue LED to stop blinking, you need to change the value of /sys/class/leds/working/trigger from "timer" to another setting. The brightness setting is backwards, so anything that's supposed to have it normally off and then blink it on briefly will do the opposite. Here are the choices which actually produced an effect during my tests rather than just keeping the LED on: Turn the LED off: echo "default-on" > /sys/class/leds/working/trigger (Alternatively, set it to "none" and then write a 1 to /sys/class/leds/working/brightness if you have plans to control it manually.) LED on except when a button is pressed on the remote: echo "rc-feedback" > /sys/class/leds/working/trigger LED on normally. Blink off to denote CPU activity above some threshold: echo "activity" > /sys/class/leds/working/trigger UPDATE: I may or may not bother trying to get the LED clock display working since I didn't keep a backup of the original firmware once I confirmed Debian was working, I only now realize it may be needed to determine which GPIO are hooked up, and I'm not particularly enthused about downloading and trying to boot one of the stock firmware images off an SD card for a display that I'd just leave off anyway because I don't like piercing blue lights in my bedroom. (My main interest was in getting it to say "boot" once more so I know when it's ready for me to SSH in, and I can get that just by turning off the blinking LED on boot completion... with the added benefit that it'll turn on steady to signal shutdown completion.)

Hello all, I just found an HK1 RBOX R1 and its remote in a box of hand-me-downs and I wanted to document what I've achieved so far for anyone else who is in my situation and turns to search engines. This is the device I'm referring to: First, my hand-me-down was missing its power supply and it doesn't say what it takes on it. Since I wound up having to learn from a photo in an Amazon Marketplace listing which isn't likely to last, the power supply is 5VDC 2A, centre positive and the barrel plug has an outside diameter of 5.5mm according to my cheap eBay calipers. The case is screwless but it spudgers open easily. Here's a photo that, among other things, shows the clip placements: Here are higher-resolution PCB shots: I followed the instructions in the initial post to flash Armbian_23.8.1_Rk3318-box_bookworm_current_6.1.50_minimal.img.xz onto it and the default settings have given me no problems so far, though I haven't really done much yet beyond setting up SSH with public key authentication, disabling root login, applying pending APT upgrades, and getting the IR remote working. (Since all my other devices except my retro-hobby LAN's NTP/Samba/Netatalk server are x86-based, I figure it'll be a nice smoke-test platform to scp ARM builds of my Rust projects onto.) Speaking of which, this is what the included remote looks like... ...and it uses the `nec` protocol. Here are the button mappings: 0x8013 OK 0x8027 Back 0x8037 Left 0x8038 Up 0x8039 Right 0x8040 Down 0x8048 LeftClick 0x8073 Home 0x8081 Power 0x8083 Menu 0x8087 Volume+ 0x8089 Volume- ...and here is an hk1_rbox_r1_remote.toml you can start from: [[protocols]] name = "HK1 RBOX R1 Remote" protocol = "nec" variant = "nec" [protocols.scancodes] 0x8013 = "KEY_ENTER" 0x8027 = "KEY_ESC" 0x8037 = "KEY_LEFT" 0x8038 = "KEY_UP" 0x8039 = "KEY_RIGHT" 0x8040 = "KEY_DOWN" 0x8048 = "BTN_LEFT" 0x8073 = "KEY_HOMEPAGE" 0x8081 = "KEY_POWER" 0x8083 = "KEY_MENU" 0x8087 = "KEY_VOLUMEUP" 0x8089 = "KEY_VOLUMEDOWN" As for things I haven't had time to read up on yet: LEDs: This thing has a blue segmented LED display on the front that, with the stock Android, shows "boot" and then switches to displaying a clock. I also need to figure out how to to make the blue status LED stop blinking once it's finished booting (See next message.) rk3318-config: Identifying what non-default settings to choose, if any ... but, for my first foray into something non-x86 beyond installing officially-vendor-supported Debian on a Cubox i4Pro, turning my old Raspberry Pi Model B into a specialized MP3 player for my mother years ago and turning my brother's Raspberry Pi 3B into a Batocera Linux box for Christmas a couple of years ago, I'd say I'm making good progress.