I got it to do something
#1
I have been trying to get the any of the BSP images to boot on the SOEDGE. I made some discoveries along the way I thought I would share. I did not see these posted anywhere else so hopefully this will help someone else.

I could not use rkflashtool on linux. It would not detect the SOEDGE while in maskrom mode. I did not troubleshoot this very far, but I think it's because it USB PID is not what rkflashtool expects. Maybe there are some udev rules that could fix this.

I tried several combinations of drivers and software on Windows 10. I eventually got the BSP image to work with the usb A to A cable.

The Rockchip tools download links in the wiki no longer work at the time I tried them. I did find a version of AndroidTool (RKDevTool) elsewhere that works. The exact version was labeled AndroidTool_Release_v2.71.zip. I used the drivers from DriverAssistant v4.5. I used the links from the Firefly Core-1808-JD4 download page.

With this combination, Androidtool was able to detect the board and flash it with the BSP images in the wiki. If you flash the Factory Test Build by Gamiee and have the touchscreen attached to the baseboard, it will boot up with a splash screen and then load a simple touch interface.

Also, like other have stated, I was not able to get the serial console working. However, adb will work. If you keep AndroidTool open and leave the usb A to A cable plugged in. It will change the detected board status from maskrom to adb after the board boots up. I used the adb_tools.zip for Radxa. With a adb start-server and adb shell, I was greeted with a prompt that was clearly the SOEDGE running.

After reading about the SOEDGE on the forum, I consider this a win as I never thought I would see this thing run code.
  Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)