RK3568-pc booting from USB

STyler

Hi
I have downloaded the correct Ubuntu core to USB and do not know how to boot to this image file.  There is a tool that I have read about that is used to make an image file (driver assist), but this is impossible to download from your site.  The google drive link works but I cannot download the file, it is not allowed.  Also, the official download does not work.  So i  cannot get the file to install onto my device.
Do you have a help file and can you email the file to use?

Liuth

356x does not support booting from USB

balbes150

Liuth Posted at 7/21/2022 05:10
356x does not support booting from USB

Supports and works well. This is implemented in a modified u-boot, which is used to run Armbian and LibreELEC on Station M2\P2 models (rk3566\rk3568). I regularly test new builds of these systems by recording images and running them directly from USB media.

STyler

OK, But when I try to load firmware image for Ubuntu I get 'failed to load' every time.  Is there another way to get Ubuntu running on this device?Also seem to be getting a 'Test Device Fail' in red.  The RKDevTool is connected to MASKROM but something is stopping me using this tool to put an OS on.

mckay115

STyler Posted at 7/21/2022 17:20
OK, But when I try to load firmware image for Ubuntu I get 'failed to load' every time.  Is there an ...

Im having the exact same issue, glad i'm not the only one at least.

Steps Im Following:
- Go to the 3568-PC Downloads Page
- Navigate to the Google Drive Ubuntu Page
- Download "Ubuntu20.04" Folder
- Unzip and navigate to the windows folder
- Run DriverAssistant_v5.11
- Change Language CFG for RKDevTool_Release_v2.92
- Run RKDevTool.exe
- Select "Upgrade Firmware" tab
- Click "Firmware" button
- Navigate to downloaded Ubuntu folder and select IMG file that was included. (ROC-RK3568-PC_Ubuntu20.04-r21156_v1.2.4a_220519.img)
- When that IMG file is loaded the following error occurs: "RKDevTool: Loading Firmware Failed!"
- The side pane shows the following note: "please check firmware if exist and occupied"


Not sure what the root of the issue is here. Any advice would be very helpful.

balbes150

>Unzip and navigate to the windows folder
>Change Language CFG for RKDevTool_Release_v2.92

As an assumption (I haven't checked), maybe you are using a non-Latin alphabet for the name\path. Try copying the firmware file to the root of the disk or directory so that the full path is without spaces and only Latin letters.

STyler

I've got a little further.
RKDevTool, in the Download Image area,make sure all the lines link to the image file.  Now it is doing something, stuck at:
'Start to download parameter...'
So now I wait, it's been nearly hr so far.....Now it has finished, and it failed.  :-(
This is just not working, I get the feeling I'll be sending it back.

mckay115

balbes150 Posted at 7/21/2022 21:05
>Unzip and navigate to the windows folder
>Change Language CFG for RKDevTool_Release_v2.92

After unpacking and moving the Ubuntu20.04 folder to the root of C:/ now the firmware file does load. Interestingly now I get the following:

Download Boot Start
Download Boot Success
Wait For Maskrom Start
Wait for Masktom Success
Test Device Start
Test Device Fail
Note: Communication issues, Certainly please check usb, Comple..........(cant see the remainder)

As of right now it seems like the unit is not starting at all. I can connect and flash the unit but it no longer has any output on the video and no lights indicate any activity.

balbes150

To check the launch from the SD card, try the systems from this topic. If desired, if everything suits you in these systems, you can install them on eMMC\SATA\NVMe and be able to run other systems from a USB or SD card.
Please note that these systems do not require any complicated steps using a cable and a special firmware program to start and install on the internal memory.
https://bbs.stationpc.com/forum. ... 6orderby%3Dlastpost

mckay115

balbes150 Posted at 7/22/2022 14:21
To check the launch from the SD card, try the systems from this topic. If desired, if everything sui ...

Would there be any reason the device fails the test? If I run ReadFlashID or ReadFlashInfo or ReadChip info or really any of the read back info it just fails. I believe once i sort what is happening here, I should have a successful flash. For some reason the unit just seems like its not leaving MaskRom mode.