Firefly Open Source Community

   Login   |   Register   |
New_Topic

How do I boot ubuntu on this board?

17

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
17
Posted at 6 day before     
I've had so much trouble.
On linux it always results in com failure. Related to udev?

On windows, the tool takes forever to download. Once downloaded, the upgrade firmware works, but still doesn't boot. If the steps from Download Image are needed, there is NO instruction where to get the files necessary.  https://wiki.t-firefly.com/en/RO ... grade_firmware.html

It should NOT be this hard to flash the device both via the computer and physically hitting the recover button between the small space at the audio jack.

I would like clear instructions on how to switch this device from android to ubuntu.
Reply

Use props Report

17

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
17
Posted at 6 day before     
Update:
Wiping firmware via eraseflash tool BUT updating firmware via Upgrade Disk Tool works. Updating firmware via RKDev tool doesn't.
Reply

Use props Report

17

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
17
Posted at 6 day before     
Also I could never wipe the firmware except from maskrom. If it was in loader, I always had to do try, let it fail, then reconnect the device.
Reply

Use props Report

17

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
17
Posted at 6 day before     
and which one is the minimal image? https://drive.google.com/drive/f ... PJmkuxFB9ylTz10Wt2l

I tried IREFLY-RK3566-ROC-PC_RTLINUX_UBUNTUUBUNTU-GPT-20210714-1024 and I can't even run apt, it has a temp fs, and the mount points are in the bad way.
FIREFLY-RK3566-ROC-PC_UBUNTU18.04-GPT-20210714-1744.7z has a desktop and I don't want that.
Reply

Use props Report

12

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
12
Posted at 5 day before     
For me this image always FAILS to download:

   FIREFLY-RK3566-ROC-PC_UBUNTU18.04-GPT-20210714-1744.img

  1. $ sudo /home/willy/rk3566/Linux_Upgrade_Tool_v1.59/upgrade_tool uf /dev/shm/FIREFLY-RK3566-ROC-PC_UBUNTU18.04-GPT-20210714-1744.img
  2. Not found config.ini
  3. Program Data in /home/willy/rk3566/Linux_Upgrade_Tool_v1.59
  4. Loading firmware...
  5. Support Type:RK3568     FW Ver:1.0.00   FW Time:2021-07-14 17:45:01
  6. Loader ver:1.01 Loader Time:2021-07-14 17:44:20
  7. Download Boot Fail
Copy the code


And yes, I also tried to erase first as indicated in the wiki. This doesn't change the outcome.

I ordered two StationPC-M2, and for now I have two bricks.

I agree with the OP, it should not be that hard to install the first OS image on such a device.
Just providing a bootable SD image is what anyone would expect, not running those bogus rockchip tools which ABSOLUTELY NEVER WORK. I even managed to get some segfaults!

Please indicate me where to download an image that was tested and that is known to be flashable, or an SD image that is able to replicate on the eMMC. I've spent all the afternoon fighting with this crap, I already regret having ordered from t-firefly :-(
Reply

Use props Report

12

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
12
Posted at 5 day before     
By the wayn @sfxworks, regarding the small space between the jack and the button, it is placed there so that you can access it through the jack using a toothpick. Just cut both ends of your toothpick and it will naturally fall on the button.
Reply

Use props Report

12

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
12
Posted at 3 day before     
So actually the reason it does not boot is that U-Boot does not see the eMMC device at all. I'm really wondering if it was installed at all!
  1. => bdinfo
  2. arch_number = 0x00000000
  3. boot_params = 0x00000000
  4. DRAM bank   = 0x00000000
  5. -> start    = 0x00200000
  6. -> size     = 0x08200000
  7. DRAM bank   = 0x00000001
  8. -> start    = 0x09400000
  9. -> size     = 0xE6C00000
  10. baudrate    = 1500000 bps
  11. TLB addr    = 0xEFFF0000
  12. relocaddr   = 0xEDD5B000
  13. reloc off   = 0xED35B000
  14. irq_sp      = 0xEB9F9020
  15. sp start    = 0xEB9F9020
  16. FB base     = 0x00000000
  17. Early malloc usage: 32f8 / 80000
  18. fdt_blob = 00000000eb9f9038

  19. => mmc list
  20. dwmmc@fe2b0000: 1
  21. dwmmc@fe2c0000: 2
  22. sdhci@fe310000: 0

  23. => mmc dev 1
  24. MMC error: The cmd index is 1, ret is -110
  25. Card did not respond to voltage select!
  26. mmc_init: -95, time 10
  27. => mmc dev 2
  28. MMC error: The cmd index is 1, ret is -110
  29. Card did not respond to voltage select!
  30. mmc_init: -95, time 51

  31. => mmc rescan
  32. MMC error: The cmd index is 0, ret is -110
  33. mmc_init: -110, time 5
Copy the code


=> this is totally bogus!
The only way I managed to flash the device was by leaving a virgin SD card in the slot. Otherwise it refuses to flash, which makes sense of course, if the eMMC is not accessible from the boot loader!

So now I have no idea what to do. I think ,I'll ask for a refund because at this level it's a real abuse, they're selling a device that cannot work at all and are blatantly lying to their customers without making any effort to provide working images nor considering their questions.
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