Firefly Open Source Community

12
New Topic

rkflashkit non-functional

77

Credits

0

Prestige

0

Contribution

registered members

Rank: 2

Credits
77
Posted at 6/22/2017 06:53:29     
I am attempting to flash the rk 3399 board using this guide: http://wiki.t-firefly.com/index.php/Firefly-RK3399/Flash_image/en

When atempting to use firefly's forked rkflashkit(0.1.4) the rk3399 is not even identified by the flashkit. Link:
https://github.com/TeeFirefly/rkflashkit

Using linuxerwang's flaskit(0.1.5) it identifies the rk3399 board but all the options are greyed out.
Screenshot from 2017-06-21 15-48-53.png

any ideas on why this is happening?

Reply

Use props Report

1821

Credits

10

Prestige

17

Contribution

super moderator

Rank: 8Rank: 8

Credits
1821
Posted at 6/22/2017 09:31:56     
1 ,did you useing the firefly-rk3399 board? or another board?
2 did you pressed the recovery button before power up?
3 have you try the maskrom mode?
Reply

Use props Report

77

Credits

0

Prestige

0

Contribution

registered members

Rank: 2

Credits
77
Posted at 6/23/2017 11:10:54     
1. I am using the RK 3399
2. i have pressed recovery key before power up
3. i have not tried masked rom mode

I am able to use android tool on windows to flash. however i still want to flash from linux(ubuntu 16)

when i try to reboot the device from command line i get :
  1. :~$ sudo rkflashkit reboot
  2. Found devices:
  3. 0x2207:0x330c
  4. libusb: error [submit_bulk_transfer] submiturb failed error -1 errno=2
  5. Traceback (most recent call last):
  6.   File "/usr/bin/rkflashkit", line 17, in <module>
  7.     sys.exit(app.main(sys.argv[1:]))
  8.   File "/usr/share/rkflashkit/lib/rkflashkit/climain.py", line 99, in main
  9.     self.parse_and_execute(args)
  10.   File "/usr/share/rkflashkit/lib/rkflashkit/climain.py", line 130, in parse_and_execute
  11.     self.reboot()
  12.   File "/usr/share/rkflashkit/lib/rkflashkit/climain.py", line 205, in reboot
  13.     op.reboot()
  14.   File "/usr/share/rkflashkit/lib/rkflashkit/rktalk.py", line 361, in reboot
  15.     self.__init_device()
  16.   File "/usr/share/rkflashkit/lib/rkflashkit/rktalk.py", line 130, in __init_device
  17.     2, ''.join(prepare_cmd(0x80, 0x00060000, 0x00000000, 0x00000000)))
  18.   File "/usr/share/rkflashkit/lib/rkflashkit/usb1.py", line 1145, in bulkWrite
  19.     return self._bulkTransfer(endpoint, data, sizeof(data), timeout)
  20.   File "/usr/share/rkflashkit/lib/rkflashkit/usb1.py", line 1129, in _bulkTransfer
  21.     raise libusb1.USBError(result)
  22. rkflashkit.libusb1.USBError: LIBUSB_ERROR_IO [-1]
Copy the code

Reply

Use props Report

35

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
35
Posted at 6/23/2017 20:50:35     
Hi cmi,
rkflashkit did not work for me either.
So I used rkdeveloptool.

  1. #!/bin/sh

  2. ../rkdeveloptool/rkdeveloptool db ../rkbin/rk33/rk3399_loader_v1.08.106.bin
  3. sleep 2
  4. ../rkdeveloptool/rkdeveloptool wl 64 idbspl.img
  5. ../rkdeveloptool/rkdeveloptool wl 512 bl3.itb
  6. ../rkdeveloptool/rkdeveloptool rd
Copy the code


Reply

Use props Report

1821

Credits

10

Prestige

17

Contribution

super moderator

Rank: 8Rank: 8

Credits
1821
Posted at 6/24/2017 09:54:26     
please use upgrade_tool for instead.
Reply

Use props Report

77

Credits

0

Prestige

0

Contribution

registered members

Rank: 2

Credits
77
Posted at 6/30/2017 11:51:08     
Last edited by cmi In 6/30/2017 11:54 Editor
fivetechno Posted at 6/23/2017 20:50
Hi cmi,
rkflashkit did not work for me either.
So I used rkdeveloptool.

Can the rkdeveloptool flash the entire packaged update image?

I am having issues with the linux_upgrade_tool as well : https://drive.google.com/file/d/0B7HO8lbGgAqAendKNTZMQlBXS2c/view

when i try to run it gives me permission denied
  1. bash: ./upgrade_tool: Permission denied
Copy the code

sudo gives me
  1. sudo: upgrade_tool: command not found
Copy the code

sudo bash gives me :
  1. upgrade_tool: upgrade_tool: cannot execute binary file
Copy the code

from what i can tell this is a 32 bit application. Is it possible that its having problems with my 64bit Ubuntu 16?
Reply

Use props Report

77

Credits

0

Prestige

0

Contribution

registered members

Rank: 2

Credits
77
Posted at 7/2/2017 05:44:16     
Found a solution using Linux_upgrade_tool 1.2 instead of 1.24 seems to work fine. Ver 1.2
Reply

Use props Report

32

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
32
Posted at 8/4/2017 03:58:53     
Last edited by brupbacher In 8/4/2017 05:25 Editor

yes works for me as well on the RK3399, how ever the upgrade_tool is somewhat tricky, i did not use the command line as described.
Instead here is what i did ...

sudo ./upgrade_tool

then you get the tools cryptic interface promting you to choose either rescan/quit or the number of the device it detected. there i just typed 1
after that you get a list of commands you can execute among them UF (or lf to low format first)

you choose (by typing) uf update.img

Now here is the tricky bit!! (i am not sure why it does not work by giving a path to the .img file)
I downloaded the ubuntu image from the firefly website (after download, extract, the result is a cryptic name starting with Firefly_RK3399...bla.img)
rename this file to update.img and move it into the directoy where the upgrade_tool is located. then restart the upgrade tool and choose 1 then when the list appears choos uf update.img ... then it starts to test and upload, when its done the firefly will restart automatically and it worked ...

fine :-)

Reply

Use props Report

22

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
22
Posted at 10/10/2017 20:27:03     
I have the same problem and I have used the recommendations here to install Linux upgrade_tool 1.2.
Everything looks right but my Ubuntu host downt recognize the RK3399 device. I have a message
“ List of rockusb connected”  no found rockusb........ and I quit.

I have downloaded Ubuntu 1604 2017 0511 1112.img from firefly website.
I have renamed and installed everything according to the information here.

I have Ubuntu 16.10 64 bit on my host.

I have tried both recommended methods with the C-connection and Recovery and Reset keys.
Nothing I do makes the my Ubuntu Host to recognize the device!?

Please advise

stentmartin

Reply

Use props Report

22

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
22
Posted at 10/11/2017 16:38:05     

I found a third method to set the device in “Loader Mode”. The method what’s totally different from the other instructions on Internet. However this time it worked and I can start the upgrade_tool and chose my device.

However when I try to low format and flash the device I get an error: “creating comm object failed”!

It seems as the memory in the device can not be formatted or flashed for some reason. Maybe the memory is protected?
There is also many different Ubuntu.img on the website. Which one is the correct to use?

The messages I have is as follows when I do “upgrade_tool uf update.img”.
1. Loading firmware
2. Support type: RK330C?? FW Ver: 6.0.01
3. Loader Version: 1.05
4. Creating comm object failed

When I try to do low format “upgrade_tool lf”, I have the following messages:
1. Lower format quit, Creating comm object failed.

Anyone else with this problem!

stentmartin

Reply

Use props Report

Return to List
12
You need to log in before you can reply Login | Register

This forum Credits Rules

Quick Reply Back to top Back to list