Luckfox Forums

Now, a very obvious issue is that the switch to SPI-NAND failed, and the image burning to SPI-NAND also failed. The successful burning was most likely to the SD card. When burning the image normally, the SD card should not be inserted, which might lead to storage recognition errors. Some subsequent problems are also likely caused by using the SPI-NAND image in the SD card. The Rk250F read in the advanced mode is also incorrect; it should be RK350F.
A lot of the information provided is inaccurate, and I can't determine where the problem lies. I suggest attaching screenshots. Also, what is Debian-HDMI-USB HOST.img? If the error location is not determined, the same operation on a new board may lead to the same problem.

Debian-HDMI-USB HOST.img is from one of your directions page :

My screenshots :

[img]blob:https://preview.redd.it/easy-guide-on-h ... 37ff31442f[/img]

Also,
-> Can you Please give me a link - to an Image that I can put on a SD Card to Boot this Lyra Zero board ?
This is my main goal.
I asked this a while ago.

Luckfox Lyra: We do not offer support for Debian. The Debian-HDMI-USB HOST.img is a boot image used on the RK3566. Based on your screenshot, the various test results are mixed together. We will first solve the problem of SD card booting.
1. Go to https://drive.google.com/drive/folders/ ... aezHE62P4z and download the illustrated image. Extract it. 2. Then download https://files.luckfox.com/wiki/Omni3576 ... _v1.78.zip with the tool. Insert the USB drive into the computer to let SDDiskTool recognize it. Select Luckfox_Lyra_Zero_W_MicroSD_250717/update.img, click SD Boot, and then click Create.
3. After the burning is completed, you can insert it into Luckfox Lyra Zero. Observe if the indicator lights start flashing. If they start flashing, it means the kernel has been entered. First, go through this process. If you encounter any problems, please save the screenshots and upload them to my reply. Do not perform any other operations, including using RKDevTool.

- Nevermind, I needed to use SdCardFormatter first.

Just received the brand new Lyra Zero.

I followed your directions and webpage :
https://wiki.luckfox.com/Luckfox-Lyra/I ... 41-windows

Boot Board holding BOOT btn / using Jumper :

RkDevTool:
Upgrade Firmware Tab:
Firmware btn
Firmware: D:\_JOHN\_EE\_MicroCPUs\LuckFox_Lyra_Zero_W\Images\Luckfox_Lyra_Zero_W_Flash_250717_MaskRom-SpiNand\update.img
Upgrade btn

SDDiskTool :
- SD 64GB
SDBoot btn
Firmware = \Ubuntu_Luckfox_Lyra_Zero_W_MicroSD_251209/update.img
Create

Repowered with SDCard :

I Firmware flashed :
Luckfox_Lyra_Zero_W_Flash_250717_MaskRom-SpiNand\update.img

Which got me to adb shell.

I booted off of both firmware & SDcard: Luckfox_Lyra_Zero_W_MicroSD_250717_BuildRoot/update.img
- but No apk-get cmds
How am I supposed to get Wireless Updates ?

The Buildroot system does not have a package manager. There are no commands like apk-update or apt-update. All software packages and libraries need to be pre-installed.

So how do I get gcc ?

I give up with this chip / board.
The support for this chip /board is minimal / not existing.

- no gcc
- no apt update cmds
- Can't even find any documentation on Pin functions - such as which pins are SPI / I2C -

Luckfox Doc (including 3566) webpages specify to use Upgrade / Update / Get-apt / Gcc cmds - so why do yo not provide them ?
Why do your Webpages give instructions to use them -if they are Not available ?
- just put the Cmds on the Image zips - so your customers can use them.

https://wiki.luckfox.com/Core3566/Core3 ... c-compiler
https://wiki.luckfox.com/luckfox-Omni35 ... Linux/#apt

-- Are you trying to upset your Customers & Clients ?

The positioning of RK3506 is different from that of RK3566. It mainly emphasizes low power consumption and stability, and completes its tasks within a lightweight customized system (such as Buildroot). Most of the time, the program is cross-compiled on the computer host and uploaded to RK3506 for execution. The board does not perform the compilation operation (and the efficiency is also very low). Therefore, we will not default to including GCC and using a system that supports package managers (such as apt) on the board side.
The apt upgrade you mentioned in the document refers to the computer used for compiling the SDK, not the actual development board itself.
The datasheet of RK3506 explains the re-mappable functions of the pins. The 40-pin pins it outputs are mostly RMIO (which can be arbitrarily re-used as SPI/I2C/CAN/UART), and these are also detailed in the wiki.
If you need a device that can directly use apt and can also perform compilation on the board with relatively high efficiency, you should choose a platform with a more advanced CPU architecture (at least not the Cortex-A7 of RK3506, and preferably an arm64 processor). All platforms will have key explanations regarding the CPU architecture to facilitate customers in determining its positioning.