TheC64 Mini doesn't boot: "cant find part named boot"

ilikec64
BASIC

Posts: 5

TheC64 Mini doesn't boot: "cant find part named boot" Oct 22, 2022 14:32:56 GMT

Quote

Post by ilikec64 on Oct 22, 2022 14:32:56 GMT

Hallo everybody,

I need help with a broken TheC64 Mini. It does not boot, the Power LED is on and the TV is showing a blank screen (but 720p signal). I connected the C64 Mini via UART to a PC and get the following messages:

HELLO! BOOT0 is starting!
boot0 version : 3.0.0
dram size =256
current block is 2 and last block is 10.
current block is 3 and last block is 10.
current block is 4 and last block is 10.
current block is 5 and last block is 10.
current block is 6 and last block is 10.
current block is 7 and last block is 10.
sum=0xe72a55a9
src_sum=0xe72a55a9
The file stored in start block 2 is perfect.
Ready to disable icache.
Jump to secend Boot.
[      0.178]
U-Boot 2011.09-rc1 (Jan 06 2018 - 10:06:55) Retro Games Ltd
[      0.185]version: 1.1.0
[      0.189]pmbus:   ready
[      0.293]PMU: AXP209
[      0.296]PMU: AXP20x found
[      0.299]PMU: bat ratio = 100
[      0.303]after set, dcdc2 =1400mv
[      0.306]PMU: dcdc2 1400
[      0.308]PMU: pll1 912 Mhz
boot_clock = 912
dcdc2_vol = 1400
[      0.316]after set, dcdc2 =1400mv
dcdc3_vol = 1250
ldo2_vol = 3000
ldo3_vol = 2800
ldo4_vol = 2800
power_start = 0
storage_type = -1
find power_sply to end
fel key old mode
run key detect
no key found
no key input
dram_para_set start
dram_para_set end
[      0.351]DRAM:  256 MiB
relocation Offset is: 05b19000
user_gpio config
user_gpio ok
DRV_DISP_Init: opened
[      0.591]fetch script data boot_disp.output_type fail
[      0.596]fetch script data boot_disp.output_mode fail
[      0.601]fetch script data boot_disp.auto_hpd fail
[      0.606]lcd0_para.lcd_used=0
workmode = 0
[      0.611]NAND: NAND_UbootInit
NAND_UbootInit start
NB1 : enter NAND_LogicInit
nand : get id_number_ctl fail, c0003
nand : get CapacityLevel fail, 4fb9e361
not burn nand partition table!
NB1 : nand_info_init fail
[      0.646]nand init fail
fail to find part named env
Using default environment
In:    serial
Out:   serial
Err:   serial
--------fastboot partitions--------
mbr not exist
base bootcmd=run setargs_nand boot_normal
bootcmd set setargs_nand
key 0
recovery key high 6, low 4
cant find fstbt value
no misc partition is found
to be run cmd=run setargs_nand boot_normal
the part isn't exist
[      0.681]Hit any key to stop autoboot:  0
cant find part named boot
sunxi_flash - sunxi_flash sub-system
Usage:
sunxi_flash read command parmeters :
parmeters 0 : addr to load(hex only)
parmeters 1 : the name of the part to be load
[parmeters 2] : the number of bytes to be load(hex only)
if [parmeters 2] not exist, the number of bytes to be load is the size of the part indecated on partemeter 1
boota: bad boot image magic, maybe not a boot.img?
redquark#

Looks like nanda / nandb is damaged, right? Is there any way to flash the nand* via this bootloader?

Last Edit: Oct 22, 2022 14:41:56 GMT by ilikec64

Deleted Deleted Member Posts: 0	TheC64 Mini doesn't boot: "cant find part named boot" Oct 22, 2022 14:43:45 GMT via mobile Quote Select Post Deselect Post Link to Post Member Give Gift Back to Top Post by Deleted on Oct 22, 2022 14:43:45 GMT thec64community.online/thread/76/2020-thec64-maxi-modding-backu Gr davy

jj0
THEC64 Developer

Manic Miner rules!

Posts: 1,053
Member is Online

TheC64 Mini doesn't boot: "cant find part named boot" Oct 22, 2022 18:05:37 GMT

Quote

Post by jj0 on Oct 22, 2022 18:05:37 GMT

The fact that it outputs:

--------fastboot partitions--------
mbr not exist

suggests that more than just nanda is damaged, it looks like the partition table in the nand is damaged. The output should look something like (depending on which nand chip your Mini has):

--------fastboot partitions--------
-total partitions:3-
-name-        -start-       -size-
boot        : 1000000       1000000
rootfs      : 2000000       7000000
UDISK       : 9000000       0
-----------------------------------

I've had something similar in the past and the only thing that helped me was to restore a backup of the entire nand. Instructions for this are in this thread, and instructions how to start in FEL mode are here.

Note: Once you are in the command line prompt in FEL mode, do not load the nand driver but (using the instructions in the first thread) first check which nand variant you have. Of course you can also do this by checking the text on the actual NAND chip. From that you can determine which nand backup to use to restore.

ilikec64
BASIC

Posts: 5

TheC64 Mini doesn't boot: "cant find part named boot" Oct 22, 2022 18:06:11 GMT

Quote

Post by ilikec64 on Oct 22, 2022 18:06:11 GMT

Oct 22, 2022 14:43:45 GMT @mrgreen36 said:

thec64community.online/thread/76/2020-thec64-maxi-modding-backu

Gr davy

Thanks for your answer, but I need more specific help. I couldn't see a hint in the post how to restore the firmware from the bootloader prompt.

ilikec64 BASIC Posts: 5	TheC64 Mini doesn't boot: "cant find part named boot" Oct 22, 2022 18:24:55 GMT jj0 likes this Quote Select Post Deselect Post Link to Post Member Give Gift Back to Top Post by ilikec64 on Oct 22, 2022 18:24:55 GMT Ok, boot up in FEL mode and try to restore the NAND from USB. I will try that in the next days and write back, if I was successful or not. Thanks for your help, jj0.

ilikec64
BASIC

Posts: 5

TheC64 Mini doesn't boot: "cant find part named boot" Oct 23, 2022 13:57:41 GMT jj0 likes this

Quote

Post by ilikec64 on Oct 23, 2022 13:57:41 GMT

Ok, the C64 Mini is running!! Here's what I did:

1. Downloaded the Nand_RW_Menu.zip flash script from here.

2. Formatted an USB pendrive to FAT32.

3. Extracted the contents of Nand_RW_Menu.zip to the root of the FAT32 pendrive.

4. Opened the C64 Mini case: removed the 4 screws under the rubber sticker, carefully opened the case (watch out for the LED connector, when opening the case). Just for easier access to the FEL mode switch.

5. Plugged in an USB keyboard and the FAT32 pendrive with the NAND_RW script to the side USB ports of the C64 Mini, as well as an TV screen to the HDMI port.

6. Pressed and hold the FEL mode key inside the C64 Mini case and connected with the other hand my (Windows 10) notebook with the C64 Mini using a USB 2.0 cable to the USB micro port on the back of the C64 Mini.

7. My (Windows 10) notebook shows now an "Unknown #1" device in the device manager.

8. Then I downloaded the Zadig USB driver tool from here.

9. Ran the Zadig Tool with the parameter described/shown here. Afterwards there was a device connected called "Allwinner SoC in FEL mode!" in my device manager.

10. The I downloaded the FEL mode boot files from here and extracted the contents to my local harddrive.

11. Next step was running the \windows\boot.cmd from the FEL mode boot files.

12. The C64 was booting into FEL mode (you can now see booting a linux with a "C64" splash screen on the TV screen).

13. After the C64 Mini was booted and a linux prompt was visible, I entered the following commands to mount the USB pendrive and started the NAND RW script:

mount /dev/sda1 /mnt
cd /mnt
./nandrw.sh

14. I checked the NAND flash type / ID with option no.1 (in my case it was an ESMT chip)

15. Back in the main menu, I choose option 3 to write the flash contents to my ESMT NAND. The NANDRW script already containing images for ESMT and Toshiba NANDs for C64 (Mini) in the corresponding subfolders.

16. The flashing took about 10 minutes (you will get a "successful" message, if everything was o.k.)

17. After that I disconnected everything from the C64, except my TV screen and connected a power supply to the back of the C64 Mini (=Micro USB port) and connected the USB Joystick to the side USB ports.

18. I powered on the C64 Mini and it was working!!

Then I check the "System Information" in the Options Menu, and the firmware version that was shown was "1.3.1". I tried to update to version 1.6.1 (the latest currently), but I stucked every time at "30%" and the rebooted the C64 Mini. For whatever reason the firmware update was not successful and the C64 was still at firmware version 1.3.1. I tried to update to 1.4.2 and the progress bar of the update run up to "100%". The the C64 rebooted automatically and the TV screen was blank!! I tried to turn it of and on again, but the C64 Mini was broken again. So I repeated all the steps above and now it's running with v1.3.1.

If somebody has an idea, why the update to 1.6.1 is not possible or the 1.4.2 update will broke my C64, please let me know.

Regards,

ilikec64

.

Last Edit: Oct 23, 2022 15:01:27 GMT by ilikec64

jj0
THEC64 Developer

Manic Miner rules!

Posts: 1,053
Member is Online

TheC64 Mini doesn't boot: "cant find part named boot" Oct 23, 2022 14:32:59 GMT via mobile

Quote

Post by jj0 on Oct 23, 2022 14:32:59 GMT

Well done 👍

As you have uart access maybe you can do a dmesg to see if there are any errors related to the nand. There might be issues with the nand.

Or try to replace the nandb partition with one that is already updated to v1.6.1, they might be included un PCUAE.

ilikec64
BASIC

Posts: 5

TheC64 Mini doesn't boot: "cant find part named boot" Oct 23, 2022 14:57:04 GMT

Quote

Post by ilikec64 on Oct 23, 2022 14:57:04 GMT

Oct 23, 2022 14:32:59 GMT jj0 said:

Well done 👍

As you have uart access maybe you can do a dmesg to see if there are any errors related to the nand. There might be issues with the nand.

Or try to replace the nandb partition with one that is already updated to v1.6.1, they might be included un PCUAE.

Thank you very much, jj0. I will check the UART messages, when updating. But not today anymore. If I get bored next weekend, I will try the update again.

spannernick
THEC64 Administrator

PCUAE Creator.. :)

Posts: 2,999

TheC64 Mini doesn't boot: "cant find part named boot" Oct 23, 2022 15:00:33 GMT

Quote

Post by spannernick on Oct 23, 2022 15:00:33 GMT

Oct 23, 2022 13:57:41 GMT ilikec64 said:

Ok, the C64 Mini is running!! Here's what I did:

1. Downloaded the Nand_RW_Menu.zip flash script from here.

2. Formatted an USB pendrive to FAT32.

3. Extracted the contents of Nand_RW_Menu.zip to the root of the FAT32 pendrive.

4. Opened the C64 Mini case: removed the 4 screws under the rubber sticker, carefully opened the case (watch out for the LED connector, when opening the case). Just for easier access to the FEL mode switch.

5. Plugged in an USB keyboard and the FAT32 pendrive with the NAND_RW script to the side USB ports of the C64 Mini, as well as an TV screen to the HDMI port.

6. Pressed and hold the FEL mode key inside the C64 Mini case and connected with the other hand my (Windows 10) notebook with the C64 Mini using a USB 2.0 cable to the USB micro port on the back of the C64 Mini.

7. My (Windows 10) notebook shows now an "Unknown #1" device in the device manager.

8. Then I downloaded the Zadig USB driver tool from here.

9. Ran the Zadig Tool with the parameter described/shown here. Afterwards there was a device connected called "Allwinner SoC in FEL mode!" in my device manager.

10. The I downloaded the FEL mode boot files from here and extracted the contents to my local harddrive.

11. Next step was running the \windows\boot.cmd from the FEL mode boot files.

12. The C64 was booting into FEL mode (you can now see booting a linux with a "C64" splash screen on the TV screen).

13. After the C64 Mini was booted and a linux prompt was visible, I entered the following commands to mount the USB pendrive and started the NAND RW script:

mount /dev/sda1 /mnt
cd /mnt
./nandrw.sh

14. I checked the NAND flash type / ID with option no.1 (in my case it was an ESMT chip)

15. Back in the main menu, I choose option 3 to write the flash contents to my ESMT NAND. The NANDRW script already containg an image for ESMT and Toshiba NANDs for C64 (Mini) in the corresponding subfolders.

16. The flashing took about 10 minutes (you will get a "successful" message, if everything was o.k.)

17. After that I disconnected everything from the C64, except my TV screen and connected a power supply to the back of the C64 Mini (=Micro USB port) and connected the USB Joystick to the side USB ports.

18. I powered on the C64 Mini and it was working!!

Then I check the "System Information" in the Options Menu, and the firmware version that was shown was "1.3.1". I tried to update to version 1.6.1 (the latest currently), but I stucked every time at "30%" and the rebooted the C64 Mini. For whatever reason the firmware update was not successful and the C64 was still at firmware version 1.3.1. I tried to update to 1.4.2 and the progress bar of the update run up to "100%". The the C64 rebooted automatically and the TV screen was blank!! I tried to turn it of and on again, but the C64 Mini was broken again. So I repeated all the steps above and now it's running with v1.3.1.

If somebody has an idea, why the update to 1.6.1 is not possible or the 1.4.2 update will broke my C64, please let me know.

Regards,

ilikec64

.

If you can not update to 1.6.1 you can always use PCUAE, it has 1.6.1 as its main carousel.

1

spannernick
THEC64 Administrator

PCUAE Creator.. :)

Posts: 2,999

TheC64 Mini doesn't boot: "cant find part named boot" Oct 23, 2022 16:07:38 GMT

Quote

Post by spannernick on Oct 23, 2022 16:07:38 GMT

Thinking about this, I do wish I could find a way of running PCUAE without it using the firmware or nand but it would need to change nanda and mount and boot the nandb image from USB, it does do that in a way in PCUAE now, it chroot the nandb image in PCUAE and mounts the nandb image depending on the model its running on but still needs the nand to be working to start PCUAE.

Last Edit: Oct 23, 2022 16:14:12 GMT by spannernick

1

jj0
THEC64 Developer

Manic Miner rules!

Posts: 1,053
Member is Online

TheC64 Mini doesn't boot: "cant find part named boot" Oct 24, 2022 11:41:25 GMT

Quote

Post by jj0 on Oct 24, 2022 11:41:25 GMT

Oct 23, 2022 16:07:38 GMT spannernick said:

Thinking about this, I do wish I could find a way of running PCUAE without it using the firmware or nand but it would need to change nanda and mount and boot the nandb image from USB, it does do that in a way in PCUAE now, it chroot the nandb image in PCUAE and mounts the nandb image depending on the model its running on but still needs the nand to be working to start PCUAE.

Yes, you can do this with my USB Boot which requires a one time update of nanda. After that you can boot whatever you want (more or less) from USB.

But for ilikec64 I would not do this unless it's clear the nand is OK, because overwriting nanda might not work in his case.

jj0
THEC64 Developer

Manic Miner rules!

Posts: 1,053
Member is Online

TheC64 Mini doesn't boot: "cant find part named boot" Oct 24, 2022 11:49:04 GMT

Quote

Post by jj0 on Oct 24, 2022 11:49:04 GMT

Oct 23, 2022 14:57:04 GMT ilikec64 said:

Oct 23, 2022 14:32:59 GMT jj0 said:

Well done 👍

As you have uart access maybe you can do a dmesg to see if there are any errors related to the nand. There might be issues with the nand.

Or try to replace the nandb partition with one that is already updated to v1.6.1, they might be included un PCUAE.

Thank you very much, jj0. I will check the UART messages, when updating. But not today anymore. If I get bored next weekend, I will try the update again.

You're welcome.

The alternative option is to manually update nandb by starting in FEL mode again, load the nand.ko driver and 'dd' a nandb v1.6.1 to /dev/nandb. But the key question is whether your nand is broken or not.

Gallery Title:
Image URL:
Image Title:
Comment:
Tick this box if you would like to allow other members to add images to your gallery.Add Image

Gallery Title:
Image URL:
Image Title:
Comment:
Tick this box if you would like to allow other members to add images to your gallery.Add Image

title

title

TheC64 Mini doesn't boot: "cant find part named boot"

Post by ilikec64 on Oct 22, 2022 14:32:56 GMT

Post by Deleted on Oct 22, 2022 14:43:45 GMT

Post by jj0 on Oct 22, 2022 18:05:37 GMT

Post by ilikec64 on Oct 22, 2022 18:06:11 GMT

Post by ilikec64 on Oct 22, 2022 18:24:55 GMT

Post by ilikec64 on Oct 23, 2022 13:57:41 GMT

Post by jj0 on Oct 23, 2022 14:32:59 GMT

Post by ilikec64 on Oct 23, 2022 14:57:04 GMT

Post by spannernick on Oct 23, 2022 15:00:33 GMT

Post by spannernick on Oct 23, 2022 16:07:38 GMT

Post by jj0 on Oct 24, 2022 11:41:25 GMT

Post by jj0 on Oct 24, 2022 11:49:04 GMT

Shoutbox