Hello, Due to authorization issues, we cannot participate in the maintenance of the Ubuntu image. You need to confirm the instructions of the author of the image you download. Generally, SDDiskTool is used for burning, refer to https://wiki.luckfox.com/Luckfox-Lyra/I ... e-flashing. Some authors may modify the structure for secondary packaging and use balenaEtcher to write the image.

Your 2 Flash Tools do NOT work for this Board on SD card.

Luckfox lyra ZERO board ???

- SocToolKit - does not see the Images / parameters
- RkdevTool - can not put multiple Images & BootFs RootFs

The Images or referred to by your luckFox Webpage :
https://wiki.luckfox.com/Luckfox-Pico-Pi/Flash-image/

Officially Supported Image Download

The Luckfox Pico Pi series provides images based on Buildroot. Users can download the image files according to their needs.

Version Description Download
Buildroot Standard models (A/B): Burn the Luckfox_Pico_Pi_EMMC_250313 firmware Wireless models (A/B W): Burn the Luckfox_Pico_Pi_W_EMMC_250313 firmware Google Driver
Community-Supported Image Download

Version Description Download
Ubuntu22.04 Standard models (A/B): Burn the Ubuntu_Luckfox_Pico_Pi_EMMC_250313 firmware Wireless models (A/B W): Burn the Ubuntu_Luckfox_Pico_Pi_W_EMMC_250313 firmware Google

I used followed your webpage directions - used RkDevTool
https://wiki.luckfox.com/Luckfox-Lyra/Image-flashing
- now my board will not Blink Led, no USB Beep ,
- nor connect via ADB ,
- nor is recognized by RkDevTool Device in Boot Mode

YOUR webpage directions - BRICKED my Board / Chip !!!
What Do I Do NOW ???

My best guess,

If you click the Update btn without an Image in RkDevtool - then I think it erases the Chip with not boot code remaining.
I accidentally did this, and I think it erased the chip.

Then the write Flash Failed : too large an Image.
You then have No Boot code on the Lyra zero.
voila - BRICKED board:
- no Led Blink
- no Win Usb Beep
- no Adp Devices connection
- no RkDevTool Devices connection

If this is true , then this should be posted (on the website directions) make sure Not to (accidentally) do this.

So how do I fix the Bricked board ?

Do you care that your RkDevTool can brick the Board, if you accidentally hit the Update btn - without an Image /or valid Image ???

Firstly, the tools used for the Luckfox Pico series and Luckfox Lyra are different. You cannot use them interchangeably. The Flash/eMMC burning for Luckfox-Lyra uses RkdevTool, while the SD card burning uses SDDiskTool. It seems that you have not used SDDiskTool.
If you encounter the prompt "too large an Image." during the burning process, it indicates that it is likely that you intended to burn the SD card image into the Flash. This burning tool will detect this and prevent it. This does not mean that your Luckfox Lyra has been damaged; it is just stuck at a certain boot stage. We have never encountered a situation where the board was damaged due to firmware burning.

If the LED light does not flash, it indicates that the kernel has not been loaded. If the USB is not recognized, it means that the usbplug.bin has not been loaded.
There are two solutions for these situations. The first one is when the wrong image was burned, the kernel has already been partially written, resulting in a failed hash check remaining in u-boot. In this case, you can long press the boot button and then press the reset button to re-enter the loader mode for burning.
The second one is that there is a problem with the loader of the image you are using. The file already in the spi-nand needs to be rewritten. In this case, you need to enter the maskrom mode for burning. You can refer to https://wiki.luckfox.com/Luckfox-Lyra/I ... th-caution to enter the maskrom mode by briefly touching the contact points.

Okay, Shorting the TestPoints put me into "Found One Maskrom Device" Mode.
-or Holding the Boot Btn Long then reset - (sometimes) did get me to below.

But I don't know what image(s) to use for the Maskrom.

"FOUND ONE MASKROM DEVICE"

Advanced Function: Boot : MiniLoaderAll.bin - Success

- All Images that I tried to use just returned
"Wait for Maskrom Failed"

Firmware: uboot.img - "Unpack Union Firmware Failed"
I tried :
Luckfox_Lyra_Flash_250717
Luckfox_Lyra_Pi_MircoSD_250717
Ubuntu_Luckfox_Lyra_MicroSD_250417
Ubuntu_Luckfox_Lyra_Zero_W_MicroSD_251209

I tried Upgrade Firmware tab:
Firmware : Debian-HDMI-USB HOST.img
=> "Download Boot Failed"

How do I get USB Boot Image on there again ?

Where do I get the 'usbplug.bin' for the Lyra Zero ?

You need to burn the image to eMMC/Spi-Nand before you can use RkdevTool. All images with "_MicroSD" cannot be used with RkdevTool.
Luckfox Lyra Zero comes with SPI-nand, and the correct one to use is Luckfox_Lyra_Zero_W_Flash_250717.zip.

I followed :
The method of erasing the SPI-NAND image using the SD card image:
1. Burn the update.img of Luckfox_Lyra_Zero_W_MicroSD onto the SD card.
2. Boot the system using the SD card.
3. Press and hold the boot button and then click the reset button to enter the download mode.
4. Open RKDevTool (only for Windows)->Advanced Function->Switch Storage->SPIAND->Erase All

Then did :

RkDevTool:
Advanced Tab:
ReadFlashID btn
Success
ReadFlashInfo btn
0 MB
ReadChipInfo :
-Rk250F
ReadCapability :
- ReadIDBConfig => 3F 07 00 00 00 00 00 00 , Disable ???
TestDevice :
- Success
GoMaskRom :
- reset Success
Boot Download btn :
- Download Boot Success
Firmware Unpack btn :
\Images\__Luckfox_Lyra_Zero_W_Flash_250717\update.img
- Android Firmware ok , dir tool
(is it Maskrom written ? - I pressed All of the buttons there)

Upgrade Firmware Tab :
Firmware btn : D:\_JOHN\_EE\_MicroCPUs\LuckFox_Lyra_Zero_W\Images\__Luckfox_Lyra_Zero_W_Flash_250717_MaskRom-SpiNand\update.img
Upgrade btn
=>
Test Device start
Test Device success
check chip start
check chip success
Get flashinfo start
Get flashinfo success
Prepare IDB start
Prepare IDB FAIL
Note please check Flash support list , welding

SpiNand , Switch Storage => Switch storage to SpiNand FAILS

EMMC , Switch Storage => Switch storage to EMMC Success

Upgrade Firmware Tab :
Firmware btn : D:\_JOHN\_EE\_MicroCPUs\LuckFox_Lyra_Zero_W\Images\__Luckfox_Lyra_Zero_W_Flash_250717_MaskRom-SpiNand\update.img
Upgrade btn
=>
Download boot Start
Download boot Success
Wait for MaskRom start
Wait for MaskRom Success
Test Device start
Test Device success
check chip start
check chip success
Get flashinfo start
Get flashinfo success
Prepare IDB Start
Prepare IDB Success
Download IDB Start
Download IDB Success
Download Firmware Start
Download Firmware (100%)...
Download Firmware Success

Upgrade Firmware Tab :
Firmware btn : D:\_JOHN\_EE\_MicroCPUs\LuckFox_Lyra_Zero_W\Images\__Luckfox_Lyra_Zero_W_Flash_250717_MaskRom-SpiNand\update.img
Upgrade btn
=> Maskrom wait FAIL

UnSolder Jumper

Re-plugin usb - no Beep

Hold Boot btn Long , release , click reset btn

RkDevTool :
Upgrade Firmware Tab :
Firmware btn :
D:\_JOHN\_EE\_MicroCPUs\LuckFox_Lyra_Zero_W\Images\Debian-HDMI-USB HOST.img
Upgrade btn :
=> Download boot Failed

Upgrade Firmware Tab :
Firmware btn : D:\_JOHN\_EE\_MicroCPUs\LuckFox_Lyra_Zero_W\Images\__Luckfox_Lyra_Zero_W_Flash_250717_MaskRom-SpiNand\update.img
Upgrade btn
=> Download boot started, Success , Maskrom wait FAIL

Download Image Tab :
0x00000000 Loader D:\_JOHN\_EE\_MicroCPUs\LuckFox_Lyra_Zero_W\Images\__Luckfox_Lyra_Zero_W_Flash_250717_MaskRom-SpiNand\MiniLoaderAll.bin
loadConfig : *
0x00000000 Parameter D:\_JOHN\_EE\_MicroCPUs\LuckFox_Lyra_Zero_W\Images\__Luckfox_Lyra_Zero_W_Flash_250717_MaskRom-SpiNand\parameter.txt
0x00000000 uboot D:\_JOHN\_EE\_MicroCPUs\LuckFox_Lyra_Zero_W\Images\__Luckfox_Lyra_Zero_W_Flash_250717_MaskRom-SpiNand\uboot.img
0x00000000 boot D:\_JOHN\_EE\_MicroCPUs\LuckFox_Lyra_Zero_W\Images\__Luckfox_Lyra_Zero_W_Flash_250717_MaskRom-SpiNand\boot.img
0x00000000 rootfs D:\_JOHN\_EE\_MicroCPUs\LuckFox_Lyra_Zero_W\Images\__Luckfox_Lyra_Zero_W_Flash_250717_MaskRom-SpiNand\rootfs.img
Press RUN btn
=> Maskrom wait FAIL


Re-Plugin uSB
- No Usb Beep


- If maskRom was written - why does Maskrom Wait FAIL ???
-- Now what ???

-

I give up with this board.
I returned it today.
I ordered another board , that will arrive in a few days.
Hopefully, we will have better luck with the board.

I and my crew hoped to introduce this board into our Robotics products.
At this point, we are having second thoughts.
If this new board does not work either, then we will have to find a board elsewhere.