console on SOEDGE Model A Baseboard

[bertiewooster]

Same experience here with a CH340 unit.  I even tried burning the images to eMMC and still nothing.  I also built images using the SDK, and those were not any different than the ones already available for download.  Any clues would be very much appreciated.

Here's my brain dump. I hope this helps.

After reading the RK1808 Technical Reference Manual (linked from the wiki), the Linux Developer Guide (in the SDK source tarball linked from the wiki), and the online docs for the Firefly RK1808 SBC (https://wiki.t-firefly.com/en/Core-1808-...arted.html) and this page at Radxa (https://wiki.radxa.com/Rock/flash_the_image), I gathered the following:

1. The SDK source tree (linked from the wiki) builds a firmware image (update.img) that contains a bootloader, kernel, and filesystem image (among other things).
   The SDK source is mostly old stuff from Rockchip from 2019 but there is also a dts file (a kind of kernel config file) for the SOEDGE board (rk1808-SoEdge.dts) that I used as a build target.

2. You need to use a USB A-to-A cable to connect your host PC and the SOEDGE baseboard USB3 port.
  On linux you can use 'upgrade_tool uf update.img' to download this to the SOEDGE flash memory.  Then presumably you can boot from it.
  There are also several Windows tools to flash the boards.  It appears that these were used at the factory but they do not run on Windows 10, at least not for me.

3. All these tools use the USB3 port on the SOEDGE baseboard so I don't think the serial console was extensively tested, if at all.
    It also appears that the kernel build includes an adb debugger that operates on the USB3 port, so more evidence for the USB3 port.

4. There are two images on the wiki but there is no information on how to boot these images.
    Method A is to burn the image to an sdcard and boot from it.  This is what I expected, coming from the Raspberry Pi world.
    Method B is to flash the firmware using the 'upgrade_tool uf update.img' approach.

5. On the Discord, the developer (gamiee) suggested Method B using the images from the wiki.  However, I was not able to get these images to boot, and I also ran into unrecoverable errors trying to flash the firmware using upgrade_tool.  The radxa and firefly wiki pages suggest erasing the firmware before reflashing in case of error but that didn't work for me.

Having said all that, I don't know if any of this is correct since I never got anything to work.

Note: If you look at the SOEDGE vs SOPINE schematics, the console is on SODIMM pins 33/34.
On SOPINE, pins 33/34 are device UART0 which goes to GPIO pins 6/8/10 on the SOPINE baseboard.
On SOEDGE, pins 33/34 are device UART2 which goes to PI-5 pins 6/8/10 on the SOEDGE baseboard; GPIO pins 6/8/10 is a different UART.
I mention this because I originally thought it was the reason I never saw the console working on the SOEDGE.
But now I'm pretty sure that I never got anything to boot.

I bought the SOEDGE boards because I wanted to experiment with the NPU on the rk1808.  I tried to work with Pine64 support and with the developer on the discord, so it was incredibly frustrating that none of the Pine64-provided software worked and no one at Pine64 could articulate the steps required to get any software working on these things.  I tried my best for 10 days and then had to return them because I literally could not get anything to work.

After more research, I learned that the rk3399Pro chip appears to have the same NPU as the rk1808, so I'm going to try again with a rk3399Pro SBC from a different vendor that appears to have more maturity on the software side.  But I'm sad that my dream of running neural nets and/or crypto miners on a cluster of SOEDGE boards is not going to come true.