Luckfox Pico Plus 更换新的Flash后,如何更改FLASH ID,从而烧录固件
Posted: 2024-06-06 9:53
更换Flash后,烧录固件时提示Write LBA faild!
A short text to describe your forum
http://forums.luckfox.com/
The cable and the computer USB port are good
Code: Select all
RKUARTDDR V1.10 ec2fae0c96 wesley.yao 22/11/15-10:58:09
S5P1
fc27
rgef0
rgef1
DDRConf1
DDR2, BW=16 Col=10 Bk=4 CS0 Row=13 CS=1 Die BW=16 Size=64MB
528MHz
DDR bin out
Boot1 Release Time: Aug 12 2022 17:14:00, version: 1.06 NO FTL
rom_version: 0x30303256
Boot from dev = 129
hamming_distance:1103 1106 2
chip_id:5256110300,0
ChipType = 27
0xff3e0040: 0x49
sfc nor id: ff ff ff
sfc_nand id: ff ff ff
Set sdmmc2 Clk: 200, 1
Set sdmmc2 Clk: 200, 1
SDC_BusRequest: CMD=1 SDC_RESP_TIMEOUT 1736
mmc2:cmd1,20
emmc reinit
Set sdmmc2 Clk: 200, 1
SDC_BusRequest: CMD=1 SDC_RESP_TIMEOUT 1736
mmc2:cmd1,20
emmc reinit
Set sdmmc2 Clk: 200, 1
SDC_BusRequest: CMD=1 SDC_RESP_TIMEOUT 1736
mmc2:cmd1,20
SdmmcInit=2 1
UsbBoot ...33728
0xff3e0040: 0x49
powerOn 38997
Code: Select all
RKUARTDDR V1.10 ec2fae0c96 wesley.yao 22/11/15-10:58:09
S5P1
fc27
rgef0
rgef1
DDRConf1
DDR2, BW=16 Col=10 Bk=4 CS0 Row=13 CS=1 Die BW=16 Size=64MB
528MHz
DDR bin out
Boot1 Release Time: Aug 12 2022 17:14:00, version: 1.06 NO FTL
rom_version: 0x30303256
Boot from dev = 129
hamming_distance:1103 1106 2
chip_id:5256110300,0
ChipType = 27
0xff3e0040: 0x49
sfc nor id: ff ff ff
sfc_nand id: ff ff ff
Set sdmmc2 Clk: 200, 1
Set sdmmc2 Clk: 200, 1
SDC_BusRequest: CMD=1 SDC_RESP_TIMEOUT 1736
mmc2:cmd1,20
emmc reinit
Set sdmmc2 Clk: 200, 1
SDC_BusRequest: CMD=1 SDC_RESP_TIMEOUT 1736
mmc2:cmd1,20
emmc reinit
Set sdmmc2 Clk: 200, 1
SDC_BusRequest: CMD=1 SDC_RESP_TIMEOUT 1736
mmc2:cmd1,20
SdmmcInit=2 1
UsbBoot ...33728
0xff3e0040: 0x49
powerOn 38997
Can you access the system via SD card? You can test with the system provided in the cloud drive.wenjie wrote: ↑2024-06-07 8:39Code: Select all
RKUARTDDR V1.10 ec2fae0c96 wesley.yao 22/11/15-10:58:09 S5P1 fc27 rgef0 rgef1 DDRConf1 DDR2, BW=16 Col=10 Bk=4 CS0 Row=13 CS=1 Die BW=16 Size=64MB 528MHz DDR bin out Boot1 Release Time: Aug 12 2022 17:14:00, version: 1.06 NO FTL rom_version: 0x30303256 Boot from dev = 129 hamming_distance:1103 1106 2 chip_id:5256110300,0 ChipType = 27 0xff3e0040: 0x49 sfc nor id: ff ff ff sfc_nand id: ff ff ff Set sdmmc2 Clk: 200, 1 Set sdmmc2 Clk: 200, 1 SDC_BusRequest: CMD=1 SDC_RESP_TIMEOUT 1736 mmc2:cmd1,20 emmc reinit Set sdmmc2 Clk: 200, 1 SDC_BusRequest: CMD=1 SDC_RESP_TIMEOUT 1736 mmc2:cmd1,20 emmc reinit Set sdmmc2 Clk: 200, 1 SDC_BusRequest: CMD=1 SDC_RESP_TIMEOUT 1736 mmc2:cmd1,20 SdmmcInit=2 1 UsbBoot ...33728 0xff3e0040: 0x49 powerOn 38997
Luckfork Pikoppleluth was unable to find the Staka version of the firmware.Crocodile wrote: ↑2024-06-07 9:02Can you access the system via SD card? You can test with the system provided in the cloud drive.wenjie wrote: ↑2024-06-07 8:39Code: Select all
RKUARTDDR V1.10 ec2fae0c96 wesley.yao 22/11/15-10:58:09 S5P1 fc27 rgef0 rgef1 DDRConf1 DDR2, BW=16 Col=10 Bk=4 CS0 Row=13 CS=1 Die BW=16 Size=64MB 528MHz DDR bin out Boot1 Release Time: Aug 12 2022 17:14:00, version: 1.06 NO FTL rom_version: 0x30303256 Boot from dev = 129 hamming_distance:1103 1106 2 chip_id:5256110300,0 ChipType = 27 0xff3e0040: 0x49 sfc nor id: ff ff ff sfc_nand id: ff ff ff Set sdmmc2 Clk: 200, 1 Set sdmmc2 Clk: 200, 1 SDC_BusRequest: CMD=1 SDC_RESP_TIMEOUT 1736 mmc2:cmd1,20 emmc reinit Set sdmmc2 Clk: 200, 1 SDC_BusRequest: CMD=1 SDC_RESP_TIMEOUT 1736 mmc2:cmd1,20 emmc reinit Set sdmmc2 Clk: 200, 1 SDC_BusRequest: CMD=1 SDC_RESP_TIMEOUT 1736 mmc2:cmd1,20 SdmmcInit=2 1 UsbBoot ...33728 0xff3e0040: 0x49 powerOn 38997
In previous tests to verify the normal operation of the product, I encountered a situation similar to yours, and ultimately found that the main control chip was short-circuited. So, please observe whether the chip heats up significantly when powered on, or use a regulated DC power supply to test if the chip is receiving power properly.
Luckfork Pikoppleluth was unable to find the SD card version of the firmware.Crocodile wrote: ↑2024-06-07 9:02Can you access the system via SD card? You can test with the system provided in the cloud drive.wenjie wrote: ↑2024-06-07 8:39Code: Select all
RKUARTDDR V1.10 ec2fae0c96 wesley.yao 22/11/15-10:58:09 S5P1 fc27 rgef0 rgef1 DDRConf1 DDR2, BW=16 Col=10 Bk=4 CS0 Row=13 CS=1 Die BW=16 Size=64MB 528MHz DDR bin out Boot1 Release Time: Aug 12 2022 17:14:00, version: 1.06 NO FTL rom_version: 0x30303256 Boot from dev = 129 hamming_distance:1103 1106 2 chip_id:5256110300,0 ChipType = 27 0xff3e0040: 0x49 sfc nor id: ff ff ff sfc_nand id: ff ff ff Set sdmmc2 Clk: 200, 1 Set sdmmc2 Clk: 200, 1 SDC_BusRequest: CMD=1 SDC_RESP_TIMEOUT 1736 mmc2:cmd1,20 emmc reinit Set sdmmc2 Clk: 200, 1 SDC_BusRequest: CMD=1 SDC_RESP_TIMEOUT 1736 mmc2:cmd1,20 emmc reinit Set sdmmc2 Clk: 200, 1 SDC_BusRequest: CMD=1 SDC_RESP_TIMEOUT 1736 mmc2:cmd1,20 SdmmcInit=2 1 UsbBoot ...33728 0xff3e0040: 0x49 powerOn 38997
In previous tests to verify the normal operation of the product, I encountered a situation similar to yours, and ultimately found that the main control chip was short-circuited. So, please observe whether the chip heats up significantly when powered on, or use a regulated DC power supply to test if the chip is receiving power properly.