I ran ADB devices and saw that it was present. This got me to the uBoot prompt and I ran the mload. Then I ran the usb_boot and changed some things to have it run putty correctly.
Then I changed (I think) 70_IMAGE so that it had the updated boot parameters and added the loads. I followed the steps for running 82_IMAGE through cpio and then repackaged it up. That said, I would think this is probably built like Android devices, so there's a potential for soft locking, but if the bootloader isn't overwritten it should be recoverable.īeta Was this translation helpful? Give feedback. This would allow us to build images which can run on the device without overwriting the nand and potentially bricking. The next step would be to not directly flash an image, but to boot from a U-Boot ramdisk. The 79_IMAGE.examples actually mentions that this is using Chromecast's kernel, so there is potentially a lot of source information to pull from. It has an architecture similar to the MV88DE3100, and the image seems to be built around that, further confirmed that the uimage is based on berlin2cdp-dongle. Interestingly, based on a quick scan of the firmware and confirmed through other research, this is the same DPU used in Chromecasts v1, v2, and Audio, as well as the Google Home and Google Home Mini. That device hardware ID now makes more sense. Maybe already common knowledge, but I hadn't seen it before, the compute module is a 88DE3006 (BG2CDP). Also discovered a lot more about the base hardware than I knew before. This has the Mrvl_WinUSB driver I was looking for.
0 kommentar(er)
