Radxa Rock Drivers on Windows 8.1

1,045 views
Skip to first unread message

Mukul Seth

unread,
Mar 4, 2014, 10:38:15 AM3/4/14
to ra...@googlegroups.com
Has anyone been able to successfully flash the Radxa Rock with Ubuntu using Windows 8.1? I tried using the RK_DriverAssistant tool and the manual driver installation method.. but the RKBatchTool cannot see the connected board. :S

Have people had success with Windows 8? Or should I suck it up, and go back to Windows 7?

Nicolas Großmann

unread,
Mar 4, 2014, 7:08:00 PM3/4/14
to ra...@googlegroups.com
Had the same problem. I tested every USB port but my laptop could not see the board. Then I switched to an older laptop and although also running with Windows 8 it worked.

Jeremy Darling

unread,
Mar 4, 2014, 11:30:45 PM3/4/14
to ra...@googlegroups.com
Nope, Windows 8.1 is a no go due to the Device Signing that Microsoft put in place.  There are a LOT of threads about hacking your drivers to get things to work, I tried them all to no avail.  Great luck on my Linux Ubuntu 13 machine.  You might try running Ubuntu in a VM with hardware passthrough enabled, then in theory you can get to the device without any issues.

mr.theski...@gmail.com

unread,
Mar 5, 2014, 4:06:10 AM3/5/14
to ra...@googlegroups.com
I'm running Ubuntu guest on top of my OpenSUSE host with VirtualBox. You have to set up the USB device filter. It's perfect.

Marco

emeric....@gmail.com

unread,
Mar 5, 2014, 7:40:35 AM3/5/14
to ra...@googlegroups.com
Le mercredi 5 mars 2014 10:06:10 UTC+1, mr.theski...@gmail.com a écrit :
> I'm running Ubuntu guest on top of my OpenSUSE host with VirtualBox. You have to set up the USB device filter. It's perfect.
>

It is also working with a VirtualBox Ubuntu 12.04 guest on top of OS X Mavericks host. Plug in a first time USB otg to enable USB filter in VirtualBox.
Note that only "Board not powered on" (http://wiki.radxa.com/Rock/recovery_mode#Board_not_powered_on) method is working for recovery mode, "Board is powering on" method doesn't.

Mukul Seth

unread,
Mar 5, 2014, 1:22:40 PM3/5/14
to ra...@googlegroups.com, emeric....@gmail.com
thx guys.. will give this a shot.. I have host Mac OS Mavericks, and guest Ubuntu 13.04 on VirtualBox. How do I enable a USB filter? Do you have a link I can refer to?

mr.theski...@gmail.com

unread,
Mar 5, 2014, 2:28:14 PM3/5/14
to ra...@googlegroups.com, emeric....@gmail.com
I don't have any link but it's an easy job.

Turn your VM off.

Go to Settings -> USB; select Enable USB Controller and Enable USB 2.0 Controller;
add the new USB filter by clicking on the first active icon on the right; select the filter and edit it.

It's important to fill in the Vendor ID and Product ID fields with the following values:

Vendor ID = 2207
Product ID = 310b

Click Ok.

Done, it should work.


Marco

Mukul Seth

unread,
Mar 12, 2014, 9:33:34 PM3/12/14
to ra...@googlegroups.com, emeric....@gmail.com
Still no luck.. the device is plugged into my USB, the USB 2.0 Controller and Filters are active, and I still get the following message when I try to run the upgrade_tool --

"No found any rockusb device,please plug device in!"

If I do >> lsusb in Ubuntu, I can see the following listing
>> Bus 001 Device 002: ID 18d1:d001 Google Inc.
Which I know is the Radxa Rock as I've seen those IDs in my Mac's System Report (Device Manager) listed under "radxa rock" while it's in Android system recovery mode.

And the Radxa is in Recovery Mode at this time, I have it plugged into my monitor and can see the recovery options on my screen.

@Marko.. You can see that the Vendor and Product IDs are different in this mode from the ones you provided, so I setup a filter using these values as well. (Vendor ID: 18d1, Product ID: d001)

Also, I've noticed that if I try to put the device in Recovery Mode while the OTG cable is plugged in, nothing happens.. Is this normal behaviour?

I can't believe I'm struggling so much with something so simple.. Would really appreciate if you guys can tell me what I'm doing wrong. :S

Is the Android Recovery Mode the same as the Radxa Rock Recovery Mode?

Tom Cubie

unread,
Mar 12, 2014, 10:02:24 PM3/12/14
to Mukul Seth, ra...@googlegroups.com, emeric....@gmail.com


On Thursday, March 13, 2014, Mukul Seth <mukul...@gmail.com> wrote:
Still no luck.. the device is plugged into my USB, the USB 2.0 Controller and Filters are active, and I still get the following message when I try to run the upgrade_tool --

"No found any rockusb device,please plug device in!"

If I do >> lsusb in Ubuntu, I can see the following listing
>> Bus 001 Device 002: ID 18d1:d001 Google Inc.
Which I know is the Radxa Rock as I've seen those IDs in my Mac's System Report (Device Manager) listed under "radxa rock" while it's in Android system recovery mode.

And the Radxa is in Recovery Mode at this time, I have it plugged into my monitor and can see the recovery options on my screen.

@Marko.. You can see that the Vendor and Product IDs are different in this mode from the ones you provided, so I setup a filter using these values as well. (Vendor ID: 18d1, Product ID: d001)

Also, I've noticed that if I try to put the device in Recovery Mode while the OTG cable is plugged in, nothing happens.. Is this normal behaviour?

I can't believe I'm struggling so much with something so simple.. Would really appreciate if you guys can tell me what I'm doing wrong. :S

Is the Android Recovery Mode the same as the Radxa Rock Recovery Mode?

No, it's different. In Android recovery mode, the kernel is running. But the radxa rock recovery mode is very low level. And from the PC side, it's different pid/vid.

To go to low level recovery mode, unplug everything of RR, press and hold recovery key, plug in the otg cable to RR and MAC. If you have vm running, it should ask you to connect this device to host or vm. Connect it to you Linux vm, then you can release the recovery key. And see if lsusb shows the device. It should be 0x0027:xxxx.
 


On Wednesday, March 5, 2014 2:28:14 PM UTC-5, mr.theski...@gmail.com wrote:
I don't have any link but it's an easy job.

Turn your VM off.

Go to Settings -> USB; select Enable USB Controller and Enable USB 2.0 Controller;
add the new USB filter by clicking on the first active icon on the right; select the filter and edit it.

It's important to fill in the Vendor ID and Product ID fields with the following values:

Vendor ID = 2207
Product ID = 310b

Click Ok.

Done, it should work.


Marco

On Wednesday, March 5, 2014 7:22:40 PM UTC+1, Mukul Seth wrote:
thx guys.. will give this a shot.. I have host Mac OS Mavericks, and guest Ubuntu 13.04 on VirtualBox. How do I enable a USB filter? Do you have a link I can refer to?

On Wednesday, March 5, 2014 7:40:35 AM UTC-5, emeric....@gmail.com wrote:
Le mercredi 5 mars 2014 10:06:10 UTC+1, mr.theski...@gmail.com a écrit :
> I'm running Ubuntu guest on top of my OpenSUSE host with VirtualBox. You have to set up the USB device filter. It's perfect.
>

It is also working with a VirtualBox Ubuntu 12.04 guest on top of OS X Mavericks host. Plug in a first time USB otg to enable USB filter in VirtualBox.
Note that only "Board not powered on" (http://wiki.radxa.com/Rock/recovery_mode#Board_not_powered_on) method is working for recovery mode, "Board is powering on" method doesn't.

--
You received this message because you are subscribed to the Google Groups "radxa" group.
To unsubscribe from this group and stop receiving emails from it, send an email to radxa+un...@googlegroups.com.
To post to this group, send email to ra...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


--
radxa rock - quad core arm computer that rocks

radxa.com

Mukul Seth

unread,
Mar 12, 2014, 10:24:02 PM3/12/14
to ra...@googlegroups.com, t...@radxa.com
Thanks Tom..

That looked liked it did the trick. :)

I flashed it with the Ubuntu Server img file.. but now when I reboot the device nothing comes up on the screen. Do I need do do something else.

This is the output from the upgrade_tool

Loading firmware...
Support Type:RK31 FW Ver:1.0.00 FW Time:2014-03-03 10:27:30
Loader ver:2.08 Loader Time:2013-12-02 18:58:57
Upgrade firmware ok.

Mukul Seth

unread,
Mar 12, 2014, 11:05:47 PM3/12/14
to ra...@googlegroups.com, t...@radxa.com
I updated the parameter to parameter_linux_only as well. Did I miss something else?

Sorry about all the noob questions. :(

Marco Fina

unread,
Mar 13, 2014, 4:54:47 AM3/13/14
to Mukul Seth, ra...@googlegroups.com

Hi Mukul,
can you open the serial console and show us the output?

Is your img the rootfs or the entire file with kernel?

Marco

Mukul Seth

unread,
Mar 13, 2014, 12:36:04 PM3/13/14
to ra...@googlegroups.com, Mukul Seth
It should be the entire file with kernel.. I'm using the following image from radxa downloads --


Now I'm trying with the dual-boot image from the following URL --


I don't have a USB-TTL cable right now.. will be picking one up tomorrow. But to the best of your knowledge which parameter/bootloader/kernel (boot.img) do I need with the dual_boot image above? If you have links, that would be great. somewhere on this site perhaps? http://dl.radxa.com/rock/images/

Or should flashing the update image alone be sufficient?

Mukul Seth

unread,
Mar 13, 2014, 12:47:27 PM3/13/14
to ra...@googlegroups.com, Mukul Seth
Flashed the dual_boot image to the nand flash, updated the parameter to parameter_dual_nand, and updated the boot_loader to the following --


The device still won't boot up. 

Could I be missing the kernel.. If so, is there an image available that I can use for the dual-boot android/ubuntu image.. If I have to build it from source, which source should I use?

Marco Fina

unread,
Mar 13, 2014, 7:06:57 PM3/13/14
to Mukul Seth, ra...@googlegroups.com

Hi Mukul,

I haven't tried these images because I'm running a custom rootfs.

Anyway, the entire update image should include the kernel, the initrd and the parameter file. So you don't need to upload other files.

Marco

Mukul Seth

unread,
Mar 14, 2014, 2:49:47 PM3/14/14
to ra...@googlegroups.com, Mukul Seth, t...@radxa.com
I picked up a TTL cable today.. and this is what I'm seeing on the debug console right now when I try to put it into recovery mode... repeated over and over...

?RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B? ...

Before this.. I was seeing a huge list of the following --

FlashReadRetry error!!,row = XXXXXXX ...

AND

LowFormat FlashReadEnhanced row = 0xXXXXXX error!!

There were A LOT of those just before it stopped going into recovery mode.. Have I managed to brick the rock? :(

Tom Cubie

unread,
Mar 15, 2014, 12:26:12 AM3/15/14
to Mukul Seth, ra...@googlegroups.com
On Sat, Mar 15, 2014 at 2:49 AM, Mukul Seth <mukul...@gmail.com> wrote:
> I picked up a TTL cable today.. and this is what I'm seeing on the debug
> console right now when I try to put it into recovery mode... repeated over
> and over...
>
> ?RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B??RK310B?

Oh, you managed to "brick" it. Don't worry, it's just the bootloader
is corrupt. You can flash any update.img to the board to unbrick it by
shortcutting the nand flash pin. The method is here:

wiki.radxa.com/Rock/unbrick

Mukul Seth

unread,
Mar 17, 2014, 3:02:18 PM3/17/14
to ra...@googlegroups.com, Mukul Seth, t...@radxa.com
I've tried the unbrick procedure about 20 times now.. still can't detect the device.. 

Keep seeing the following...

>> List of rockusb connected
>> No found rockusb,Rescan press <R>,Quit press <Q>:

And the debug console keeps showing repeated ?RK310B? as before.. :(

Naoki FUKAUMI

unread,
Mar 17, 2014, 6:10:14 PM3/17/14
to ra...@googlegroups.com
On Tuesday, March 18, 2014 4:02:18 AM UTC+9, Mukul Seth wrote:
I've tried the unbrick procedure about 20 times now.. still can't detect the device.. 

Keep seeing the following...

>> List of rockusb connected
>> No found rockusb,Rescan press <R>,Quit press <Q>:

And the debug console keeps showing repeated ?RK310B? as before.. :(

I think, while console shows ?RK310B?, you should be able to see device as mask rom mode w/o shorting NAND pins.

it may be better to run "upgrade_tool ef", but I guess you cannot flash anything now, right?
then, how about flashing from SD card?

Tom Cubie

unread,
Mar 18, 2014, 12:30:12 AM3/18/14
to Mukul Seth, ra...@googlegroups.com
Hi, the new 3.7 window driver should works on win8/8.1.
You can download it here:
http://dl.radxa.com/rock/tools/windows/Rockusb%20Driver%20v3.7.zip

But... the new driver needs the new bootloader loader version 2.x...
So, if you are using older bootloader... You will have to upgrade the
bootloader first, via sd upgrading or in other pcs.

>
> --
> You received this message because you are subscribed to the Google Groups
> "radxa" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to radxa+un...@googlegroups.com.
> To post to this group, send email to ra...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.

Eric Wang

unread,
Mar 19, 2014, 1:47:20 AM3/19/14
to ra...@googlegroups.com
After tested with driver ver. 3.7 with bootloader 2.08 ok for win8.1, but the RKDevelopTool_v1.37 and BatchTool can't found the device...
any idea?



Mukul Seth於 2014年3月4日星期二UTC+8下午11時38分15秒寫道:
Reply all
Reply to author
Forward
0 new messages