Luckfox Forums

I have a problem with the Pico Plus. I can load Busybox, Buildroot, Alpine, but I can't load Ubuntu from SD. I can't erase the NAND from SocToolKit. I've tried various SD cards and writing is fine, but the pico starts as if it were not there, even if hot-plugging it detects it. I followed this page step by step https://wiki.luckfox.com/Luckfox-Pico/L ... burn-image. Include some screenshots. I wonder if my pico is defective. Many thanks.

Hello To erase spi-nand, you need to click DownloadBin and then click Erase All, Luckfox Pico Plus does not support hot swapping of SD cards, if conditions permit, you can replace other models of SD cards for testing, pay attention to the CLASS10 requirements of SD cards

I can't solve the problem. New SD, it seems like it's not recognized by kernel
[root@luckfox root]# dmesg | tail -n 30
[ 3.013003] mpp_vepu_pp ffa60000.rkvenc-pp: probing finish
[ 3.013341] mpp_service mpp-srv: probe success
[ 3.042489] RKNPU ff660000.npu: RKNPU: rknpu iommu device-tree entry not found!, using non-iommu mode
[ 3.043162] RKNPU ff660000.npu: RKNPU: Initialized RKNPU driver: v0.9.2 for 20230825
[ 3.043281] RKNPU ff660000.npu: dev_pm_opp_set_regulators: no regulator (rknpu) found: -19
[ 3.130669] rockit_load start
[ 3.150327] rockit_load end
[ 3.171400] rve: rve_irq, irq = 52, match scheduler
[ 3.172078] rve: Driver loaded successfully rve[2] ver:[2021]58.1a
[ 3.172103] rve: probe successfully
[ 3.173979] rve: Module initialized. v1.0.6
[ 3.531434] rk_gmac-dwmac ffa80000.ethernet eth0: PHY [stmmac-0:02] driver [RK630 PHY] (irq=POLL)
[ 3.531840] dwmac4: Master AXI performs any burst length
[ 3.531869] rk_gmac-dwmac ffa80000.ethernet eth0: No Safety Features support found
[ 3.531892] rk_gmac-dwmac ffa80000.ethernet eth0: PTP not supported by HW
[ 3.532243] rk_gmac-dwmac ffa80000.ethernet eth0: configuring for phy/rmii link mode
[ 3.873636] file system registered
[ 3.912293] using random self ethernet address
[ 3.912323] using random host ethernet address
[ 3.926513] Mass Storage Function, version: 2009/09/11
[ 3.926546] LUN: removable file: (no medium)
[ 4.004177] read descriptors
[ 4.004399] read strings
[ 5.009001] usb0: HOST MAC fe:97:ec:7d:82:a6
[ 5.009030] usb0: MAC 56:fb:f7:b6:09:74
[ 5.118304] dwc3 ffb00000.usb: device reset
[ 5.219238] android_work: sent uevent USB_STATE=CONNECTED
[ 5.294256] android_work: sent uevent USB_STATE=CONFIGURED
[ 5.606997] rk_gmac-dwmac ffa80000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
[ 6.653383] OF: overlay: WARNING: memory leak will occur if overlay removed, property: /mmc@ffaa0000/status
[root@luckfox root]#

Welcome to Alpine for Luckfox!

login[548]: root login on 'ttyFIQ0'
Luckfox:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
mtdblock0 31:0 0 256K 0 disk
mtdblock1 31:1 0 256K 0 disk
mtdblock2 31:2 0 512K 0 disk
mtdblock3 31:3 0 4M 0 disk
mtdblock4 31:4 0 120M 0 disk
Luckfox:~#

Please use the image provided in our network disk to insert the SD card and attach the complete boot log (you can use the serial port module to obtain or execute cat /var/log/messages to obtain), do not use luckfox-config and check if there is a /dev/mmcblk1 device

file downloaded from https://drive.google.com/drive/folders/ ... 7lHgp9PaFS tested with 5 different sd.Ubunti version for Picoplus. Add file boot.

From the logs, it seems that the initialization of the SD card timed out when sending the CMD13 instruction (SD_CMD_APP_SD_STATUS), which is used when reading the SD card ssr, which is the first time that the data pin is used after initializing with the CMD and CLK pins. In the kernel log, the information of the SD card was also obtained through the CMD pin, but an IO error occurred when the SD card was read through the data pin.
I speculate that it should be a hardware problem, the data pin of the Luckfox pico is damaged or the SD card holder is damaged, it should be noted that the SD pin of the Luckfox Pico Plus is led out to the pin header, if there is a connected device on the pin, this phenomenon may also occur

I sincerely thank the forum for the support provided. The issue was hardware-related, so I decided to purchase a new board, but the assistance offered was nonetheless very helpful.