Firefly Open Source Community

   Login   |   Register   |
New_Topic

[General] Bricked SoC ? Stuck in MaskROM mode, unable to update firmware

93

Credits

0

Prestige

0

Contribution

registered members

Rank: 2

Credits
93
Posted at 4/23/2024 23:43:26     
I hope my mistake can be repaired. Some weeks ago I seemingly bricked my RK3399 SoC, because I followed an advice from some internet tutorial advising to erase some blocks using an upgrade_tool ws 0xsome_address /dev/null or something like that. It was a rather small address.

Since then I can only boot in MaskROM mode, but what worries me the most is that the size of the flash memory is displayed to be zero :
  1. sudo ./upgrade_tool rfi

  2. Flash Info:

  3.         Manufacturer: SAMSUNG,value=00
  4.         Flash Size: 0MB
  5.         Block Size: 512KB
  6.         Page Size: 2KB
  7.         ECC Bits: 0
  8.         Access Time: 40
  9.         Flash CS:
Copy the code

Also I cannot simply wipe out / upgrade the emmc firmware like I used to do :

  1. sudo ./upgrade_tool uf ffly/stock/FIREFLY-RK3399_Ubuntu20.04-r240_v2.5.1d_230330.img
  2. Program Log will save in the /root/upgrade_tool/log/
  3. Loading firmware...
  4. Support Type:RK330C     FW Ver:8.1.00   FW Time:2023-03-30 16:11:48
  5. Loader ver:1.1a Loader Time:2023-03-30 16:11:20
  6. Download Boot Fail
Copy the code

Is there a way to solve this and hard reset the SPI/emmc ? Probably using the electric pins ? Thank you.

PS I don't mind which platform to use, this is posted from Linux using manjaro live usb but I have a spare Windows computer among others.

Reply

Use props Report

93

Credits

0

Prestige

0

Contribution

registered members

Rank: 2

Credits
93
Posted at 5/30/2024 01:39:19     
Hello ? Can anyone tell me whether I can fix my own card, or else if I need to return it to the staff for repairing ?
Reply

Use props Report

93

Credits

0

Prestige

0

Contribution

registered members

Rank: 2

Credits
93
Posted at 7/9/2024 07:32:23     
I opened a thread on r/SBCs.

rkflashtool on MacOS gives the most information: this is what I get after having booted the card in Maskrom mode and attempted to write/update the emmc:

  1. sylvansab@mac ~ % cd hack/ffly/ubuntu-image
  2. sylvansab@mac ubuntu-image % l
  3. CLIoutImageMiniLoaderAll.binpackage-fileparameter.txt
  4. sylvansab@mac ubuntu-image % rkflashtool w miniloader <MiniLoaderAll.bin
  5. rkflashtool: info: rkflashtool v6.1
  6. rkflashtool: info: Detected RK3399...
  7. rkflashtool: info: interface claimed
  8. rkflashtool: info: MASK ROM MODE
  9. libusb: warning [darwin_transfer_status] transfer error: device not responding (value = 0xe00002ed)
  10. libusb: warning [darwin_transfer_status] transfer error: device not responding (value = 0xe00002ed)
  11. rkflashtool: info: working with partition: miniloader
  12. libusb: error [submit_bulk_transfer] bulk transfer failed (dir = Out): pipe is stalled (code = 0xe000404f)
  13. libusb: error [submit_bulk_transfer] bulk transfer failed (dir = In): pipe is stalled (code = 0xe000404f)
  14. libusb: error [submit_bulk_transfer] bulk transfer failed (dir = In): pipe is stalled (code = 0xe000404f)
  15. rkflashtool: fatal: invalid size of parameter block
  16. sylvansab@mac ubuntu-image % rkflashtool w 0x40 MiniLoaderAll.bin
  17. rkflashtool: info: rkflashtool v6.1
  18. rkflashtool: info: Detected RK3399...
  19. rkflashtool: info: interface claimed
  20. rkflashtool: info: MASK ROM MODE
  21. libusb: warning [darwin_transfer_status] transfer error: device not responding (value = 0xe00002ed)
  22. libusb: warning [darwin_transfer_status] transfer error: device not responding (value = 0xe00002ed)
  23. ... Done!
  24. sylvansab@mac ubuntu-image % rkflashtool w 0x4000 Image/boot.img
  25. rkflashtool: info: rkflashtool v6.1
  26. rkflashtool: info: Detected RK3399...
  27. rkflashtool: info: interface claimed
  28. rkflashtool: info: MASK ROM MODE
  29. libusb: warning [darwin_transfer_status] transfer error: device not responding (value = 0xe00002ed)
  30. libusb: warning [darwin_transfer_status] transfer error: device not responding (value = 0xe00002ed)
  31. ... Done!
Copy the code
Reply

Use props Report

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

This forum Credits Rules

Quick Reply Back to top Back to list