Page 1 of 1
RKdev Tool does not work
Posted: Sun Oct 30, 2022 7:16 pm
by Dysmas
I have a R5S used for development. I loaded in eMMC an image which failed. It has an uboot loader, and for this reason it is no longer possible to boot on a SD card without masking the eMMC. The only possible way to repair the device is to use the tool RKdev. Everything I tried failed.
Connection is OK, I see "Found one MASKROM Device".
I tried to send the MiniLoaderAll.bin I see :
Downoad boot start
Download boot failed
All other options show : Test device start / Test device failed
Dev Partition returns : Failed to read partition table
Everything I try send an error message.
I was able to load a firmware under the tab Upgrade Firmware, but when I click Erase Flash (which is what I want), I get the message
Download Boot FailedWas anyone able to use this tool ?
Re: RKdev Tool does not work
Posted: Sat Nov 05, 2022 5:42 pm
by MichaIng
Similar here: Sadly in my case, additionally also loading any other OS image from "Upgrade Firmware" tab > "Firmware" button (tried with a custom one, as well as the official R5S Debian image) fails with "Loading firmware failed!".
"EraseFlash", any erase or read info button from "Advanced Function", as well as "Dev Partition" from "Download Image" all fail.
The problem is that, as of testing and developing a custom image, I currently have an unbootable image on the eMMC (flashed when booted from functional SD card). Since it uses no FriendlyELEC bootloader, it is preferred and hence boot always fails as long as maskrom botton is not pressed while functional image on SD card attached. With pressed maskrom, however, the eMMC isn't accessible from booted SD card system either, so I cannot flash any image to eMMC from there. With the drivers/RKdev tool not working, I have now not any option to flash anything else to eMMC and am doomed to press the maskrom button on every boot/reboot from SD card.
Re: RKdev Tool does not work
Posted: Wed Nov 09, 2022 6:33 am
by usual user
If the maskrom botton is released while the first firmware messages are displayed on the serial console, the booting system can probe the eMMC and it will be accessible. Of course, the booting system must support eMMC access.
Re: RKdev Tool does not work
Posted: Thu Nov 24, 2022 4:02 pm
by MichaIng
Thanks, indeed on another attempt I recognised that the eMMC drive was visible from the SD card booted system. So timing is the key here
.
Would be still great if flashing via USB would work, to not rely on a system on SD card.
Re: RKdev Tool does not work
Posted: Sun Dec 11, 2022 9:40 am
by Dysmas
Unfortunately, I have been unable to reproduce what you say : even with the shortest time possible which allows booting on the SD card, the eMMC is not visible. I sent a message to the technical support but never got an answer. Excellent device, but total lack of technical support. This is regrettable.
Re: RKdev Tool does not work
Posted: Sun Dec 11, 2022 11:47 am
by usual user
Without providing a serial console log collected via the debug UART, no one knows what's going on and no more comprehensive support can be provided.
Re: RKdev Tool does not work
Posted: Tue Jan 17, 2023 5:41 pm
by Dysmas
usual user wrote:
Without providing a serial console log collected via the debug UART, no one knows what's going on and no more comprehensive support can be provided.
I don't think UART data is useful. There is no problem about the boot process, it is very well known : if a system with a non Friendly Elec is loaded on the eMMC, the device will always boot from the eMMC, never from the SD card. This is by design. If this system starts booting and fails, there is no way to start the device with access to eMMC. The only way to start from the SD card is to mask the eMMC. But then, you no longer see it and it is not possible to erase it. All this is normal and by design.
RKdev Tool was offered to provide a way to load something on the eMMC without booting, or to erase the eMMC to regain the possibility to start from SD card. But this tool always fails, and this is our question. I doubt UART will show anything about it. But there is a log file. Here is a typical example, after use of several commands.
Code: Select all
22:10:13 457 LoadConfig-->PathFileExists Chinese.ini failed
22:11:21 400 LoadConfig-->PathFileExists Chinese.ini failed
22:12:57 256 RKDevTool v2.8.4.0 start run
22:13:13 426 RKDevTool v2.8.4.0 start run
22:14:27 402 RKDevTool v2.8.4.0 start run
22:14:42 256 Error:RKU_Write-->WriteFile failed,bRet=0,err=31,size=31,write=0
22:15:04 260 INFO:RKU_ResetPipe-->DeviceIoControl OK
22:15:04 261 Error:RKU_Write-->WriteFile failed,bRet=0,err=31,size=31,write=0
22:15:21 840 Error:RKU_Write-->WriteFile failed,bRet=0,err=995,size=31,write=0
22:15:23 842 ERROR:RKU_ResetPipe-->DeviceIoControl failed,err=31
22:15:23 843 <LAYER 3-1> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-3),path=\\?\USB#VID_2207&PID_350A#5&3167A853&0&1#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
22:15:29 845 Error:RKU_Write-->WriteFile failed,bRet=0,err=995,size=31,write=0
22:15:31 846 ERROR:RKU_ResetPipe-->DeviceIoControl failed,err=31
22:15:31 847 <LAYER 3-1> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-3),path=\\?\USB#VID_2207&PID_350A#5&3167A853&0&1#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
22:15:37 850 Error:RKU_Write-->WriteFile failed,bRet=0,err=995,size=31,write=0
22:15:39 851 ERROR:RKU_ResetPipe-->DeviceIoControl failed,err=31
22:15:39 852 <LAYER 3-1> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-3),path=\\?\USB#VID_2207&PID_350A#5&3167A853&0&1#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
22:15:50 581 Error:RKU_Write-->WriteFile failed,bRet=0,err=995,size=31,write=0
22:15:52 583 ERROR:RKU_ResetPipe-->DeviceIoControl failed,err=31
22:15:52 584 Error:ResetDeviceProc-->RKU_ResetDevice failed,err=-3
22:16:03 664 Error:RKU_Write-->WriteFile failed,bRet=0,err=995,size=31,write=0
22:16:05 666 ERROR:RKU_ResetPipe-->DeviceIoControl failed,err=31
22:16:05 667 Error:ResetMaskromProc-->RKU_ResetDevice failed,err=-3
22:16:17 002 Error:RKU_Write-->WriteFile failed,bRet=0,err=995,size=31,write=0
22:16:17 002 Error:ListStorageProc-->RKU_ReadCapability failed,err=-3
22:16:29 525 Error:RKU_Write-->WriteFile failed,bRet=0,err=995,size=31,write=0
22:16:29 526 Error:DetectSMProc-->RKU_ReadCapability failed,err=-3
22:16:39 684 Error:RKU_Write-->WriteFile failed,bRet=0,err=995,size=31,write=0
22:16:44 688 Error:RKU_Write-->WriteFile failed,bRet=0,err=995,size=31,write=0
22:16:46 689 ERROR:RKU_ResetPipe-->DeviceIoControl failed,err=31
22:16:46 690 Error:ExportImageProc-->RKU_ReadComData failed,err=-3
22:17:04 732 Error:Loading boot failed,err=-1
22:17:12 650 RKDevTool v2.8.4.0 start run
22:17:26 115 Error:RKU_Write-->WriteFile failed,bRet=0,err=995,size=31,write=0
22:17:58 438 Error:RKU_Write-->WriteFile failed,bRet=0,err=995,size=31,write=0
22:18:00 439 ERROR:RKU_ResetPipe-->DeviceIoControl failed,err=31
22:18:00 440 ERROR:ErasePartition-->RKU_ReadFlashID failed,err=-3
22:18:18 911 Error:RKU_Write-->WriteFile failed,bRet=0,err=995,size=31,write=0
22:18:20 912 ERROR:RKU_ResetPipe-->DeviceIoControl failed,err=31
Re: RKdev Tool does not work
Posted: Wed Jan 18, 2023 1:06 pm
by Dysmas
I tried with an older version of RKDevTool (2.58). The result is the same.
14:00:44 896 Error:RKU_Write-->WriteFile failed,bRet=0,err=31,size=31,write=0
14:00:57 442 ERROR:RKU_ResetPipe-->DeviceIoControl failed,err=995
14:00:57 443 <LAYER 1-1-3> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-3),path=\\?\USB#VID_2207&PID_350A#6&1B228727&0&3#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
14:01:03 445 Error:RKU_Write-->WriteFile failed,bRet=0,err=995,size=31,write=0
14:01:15 452 ERROR:RKU_ResetPipe-->DeviceIoControl failed,err=995
14:01:15 453 <LAYER 1-1-3> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-3),path=\\?\USB#VID_2207&PID_350A#6&1B228727&0&3#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
14:01:21 455 Error:RKU_Write-->WriteFile failed,bRet=0,err=995,size=31,write=0
14:01:23 457 ERROR:RKU_ResetPipe-->DeviceIoControl failed,err=31
14:01:23 458 <LAYER 1-1-3> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-3),path=\\?\USB#VID_2207&PID_350A#6&1B228727&0&3#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
14:01:51 043 Error:RKU_Write-->WriteFile failed,bRet=0,err=995,size=31,write=0
14:01:53 045 ERROR:RKU_ResetPipe-->DeviceIoControl failed,err=31
14:01:53 046 Error:ResetMaskromProc-->RKU_ResetDevice failed,err=-3
14:02:00 889 Error:RKU_Write-->WriteFile failed,bRet=0,err=995,size=31,write=0
14:02:02 890 ERROR:RKU_ResetPipe-->DeviceIoControl failed,err=31
14:02:02 891 Error:ResetDeviceProc-->RKU_ResetDevice failed,err=-3
14:02:30 657 Error:CheckDownloadItem--> is not existed!
14:02:33 800 Layer<>: RunProc is ending, ret=0
14:02:44 149 Error:RKU_Write-->WriteFile failed,bRet=0,err=995,size=31,write=0
14:02:46 150 ERROR:RKU_ResetPipe-->DeviceIoControl failed,err=31
14:02:46 152 Error:ReadDevicePartTableProc-->During checking gpt or parameter RKU_ReadLBA failed,err=-3
14:03:09 476 Error:RKU_Write-->WriteFile failed,bRet=0,err=995,size=31,write=0
14:03:11 477 ERROR:RKU_ResetPipe-->DeviceIoControl failed,err=31
14:03:11 478 Error:ReadChipInfoProc-->RKU_ReadChipInfo failed,err=-3
14:03:18 852 Error:RKU_Write-->WriteFile failed,bRet=0,err=995,size=31,write=0
14:03:18 853 Error:ReadCapabilityProc-->RKU_ReadCapability failed,err=-3
Is there a way to "redeem" a R5S or R5C with a bad system on eMMC ?
Re: RKdev Tool does not work
Posted: Thu Jan 19, 2023 11:37 am
by starsconty
Thanks, indeed on another attempt I recognised that the eMMC drive was visible from the SD card booted system. So timing is the key here
.
Re: RKdev Tool does not work
Posted: Mon Apr 03, 2023 4:13 pm
by Dysmas
Fortunately, there is now another solution. With a recent eFlasher, even if I had to mask the eMMC to start it from the SD card, it was able to recognize the eMMC and to flash a FriendlyElec OS on it. So the problem is now solved for me.
Re: RKdev Tool does not work
Posted: Thu Aug 17, 2023 12:44 pm
by Danalberto231
Thanks, indeed on another attempt I recognised that the eMMC drive was visible from the SD card booted system. So timing is the key here
.
Hubspot partner agency
Mehendi designs