- #Arduino ch341 serial driver linux 3.16.0 serial#
- #Arduino ch341 serial driver linux 3.16.0 drivers#
- #Arduino ch341 serial driver linux 3.16.0 android#
After some bad flashing, (bad why? no idea, rkflashtool or upgrade_tool both successfully report the flashing complete, then I reboot, and get…. Oh yeah, the “thing that has stuck out” Despite being “unbrickable” because they have a maskrom bootloader, and normally just going into recovery mode, I’ve had great difficulty.
#Arduino ch341 serial driver linux 3.16.0 serial#
The serial console is in the picture below.īottom side, spectek flash, serial console details and yeah, again, thanks for nothing rockchip. On a cp2102 serial dongle, you’ll need to use the silabs baud rate aliasing software to get to this baud rate. First, the default serial console is at 1500000 baud. The “system.img” wil be a raw ext4 image (in theory) and you can mount it locally to explore with “sudo mount -o loop blah.img somemountpoint”Īnyway, while some of this is just for my own notes, not really for anyone else, one thing has stuck out. Documentation on what’s what is less than forthcoming. you’ll probably have to unpack more than once. If you have a stock firmware, (“update.img”) you can use rkunpack from the rkflashtool repository.
#Arduino ch341 serial driver linux 3.16.0 android#
You can in theory extract the modules from your android system image. Why the fuck rockchip is keeping _this_ bit proprietary is beyond me.
#Arduino ch341 serial driver linux 3.16.0 drivers#
Except, because some of the drivers are actually separate binary proprietary modules, you end up needing a fucking initrd/initramfs timewaste so it can have such core details like a functional fucking nand driver. It has support for all your hardware, you just need to replace the root file system (RFS) and amend the kernel command line to say where your rootfs is. If you just want to run linux, in _theory_ you can just use the existing android kernel shipped stock. I’ve still no idea, but some things seem a little clearer than last time… maybe? A garbage world of “custom roms” and complicated documentation detailing multiple ways of doing things with rarely any explanation of why. And I’ve not worked on amlogic or sunxi chips, but goddamn, the work environment is still just as sucky. Note: My copy of this device has a much smaller heatsink, Spectek flash, not Sandisk, and some generic no name ram chips. I still believed that rockchip was doing the best job of upstream support. New hotness I thought, but the cheap end. Rockchip continued to contribute upstream, so I bought a MXQ 4K (RK3229). Little tiny cute black boxes, with a remote control and a power supply and ethernet and usb shipped for $30? That’s what I want to reuse. Raspi3 is at least decently powerful, but running everything off a sdcard, and not having a case is really not what I was looking for. The plan was to use the swell of consumer electronics to get a cheap android tv box that I could run linux on, and use as a small home server. However, the RK3066 just missed the boat, and while I poked and prodded a bit, it was all just a bit too difficult and a bit too complicated a bit too much not much fun. Back when I bought a RK3066 based device, I had seen rockchip developers start contributing directly upstream.