Not really clear on how to flash this. It has to be done through an external PC or it can be done from the Renegade elite? Obviously, libudev1:i386 won't run on an ARM chipset like the RK3399?
well, it does seems it needs to be a external 32-bit compat. (i386) linux computer to be able to use the upgrade_tool : that's not that bad, it's knowing whether it was previously SPI flashed or not to get the UART console/keyboard interaction. and then messing with the two pin.
so, you have to use a USB-C or a USB 3.0 to USB-C cable on Jack labelled (TYPE C0) the USB-C(0)(power) Port next to the HDMI port, this powers the RK3399 and it becomes a USB device which gets listed by linux as the new device with (lsusb): Bus 002 Device 002: ID 2207:0006 Fuzhou Rockchip Electronics Company Firefly
That's what I thought, problem is I don't really have a PC to mess around with, so it complicates things for me. My only 2 laptops are corporate laptops and they're more locked down than fort Nox. I COULD set things up on my rpi4, I guess. It's just logistics that becomes complicated. Had it been a windows flash tool, I wouldn't have this discussion, mind you. But it's fine. I get it.
Ok, so considering this was a trial an error, here is the method to flash this package on a PC that can't boot a 32 bit OS: Make a USB live disk (Ubuntu amd64 is just fine) Install 32 bit architecture with commands below. I can flash mainline or rockchip separately, but can't flash both as the documentation specifies, but at least the updater works.
Once done, you can run the commands in the text file. Also tested the SPI NOR reset trick by shorting 2 pins, works fine... Also, if you installed the mezannine, get ready to uninstall it, because the SPI NOR is on the main board. @loverpi - Please answer my emmc question and please explain why I can't flash Rockchip after mainline? Should they both be flashed or only one of the two? It gets stuck on Download Boot and doesn't move forward.
Ok, so now I'm getting "The device did not support this operation!" when running the first line, which runs upgrade_tool db ../rk3399_loader_spinor_v1.14.114.bin... Both scripts run, both scripts give this error, still can't get into u-boot... Sigh.
So back to normal. Tried combining both flash scripts, still no dice. Tried flashing mainline, booting the board, no dice. Tried flashing rockchip and booting the board, no dice.
Ok, so just flashed the rockchip SPI NOR, booted in u-boot FINALLY. I thought it was weird that addressing was similar on both scripts, so they just can't seem to be flashed together, just one or the other. Takes about 20 seconds to get a display. Lots of errors on load up script... Detects USB devices... Based on u-boot 2017-09 dirty. Progress, I guess...
Comments
that's not that bad, it's knowing whether it was previously SPI flashed or not to get the UART console/keyboard interaction.
and then messing with the two pin.
Bus 002 Device 002: ID 2207:0006 Fuzhou Rockchip Electronics Company Firefly
Had it been a windows flash tool, I wouldn't have this discussion, mind you. But it's fine. I get it.
What I'd rather get an answer to is where my emmc shipment is at??
Make a USB live disk (Ubuntu amd64 is just fine)
Install 32 bit architecture with commands below. I can flash mainline or rockchip separately, but can't flash both as the documentation specifies, but at least the updater works.
Once done, you can run the commands in the text file. Also tested the SPI NOR reset trick by shorting 2 pins, works fine... Also, if you installed the mezannine, get ready to uninstall it, because the SPI NOR is on the main board.
@loverpi - Please answer my emmc question and please explain why I can't flash Rockchip after mainline? Should they both be flashed or only one of the two? It gets stuck on Download Boot and doesn't move forward.