|
Post by mguru on Mar 18, 2021 19:41:15 GMT
Hello,
I received recently broken c64mini. Because I hate to just throw away broken things I'm trying to repair it. So I connected USB-UART to onboard UART and this is output:
HELLO! BOOT0 is starting!
boot0 version : 3.0.0
dram size =256
ERROR! block 2 doesn't store head of Boot1 copy.
ERROR! block 3 doesn't store head of Boot1 copy.
ERROR! block 4 doesn't store head of Boot1 copy.
ERROR! block 5 doesn't store head of Boot1 copy.
ERROR! block 6 doesn't store head of Boot1 copy.
ERROR! block 7 doesn't store head of Boot1 copy.
nand block 8 is bad
nand block 9 is bad
nand block 10 is bad
Can't find a good Boot1 copy in nand.
Ready to quit "load_Boot1_from_nand".
Ready to disable icache.
Jump to Fel. So I thought: "ok, nand looks like is bad, but maybe I'll be able to start FEL recovery and try to repair NAND with nand_rw". But after runningvboot.cmd from C64Mini-FEL-boot-v1.1 I got:
U-Boot SPL 2018.05-jj_0+ (Dec 21 2018 - 20:27:20 +0100)
DRAM: 0 MiB
CPU: 912000000Hz, AXI/AHB/APB: 3/2/2
Trying to boot from FEL ... and that's it. I stuck here. What worries me is "DRAM: 0 MiB". Is that's what is supposed to be when running boot.cmd? I suppose that BOOT0 is also in NAND or I'm wrong? Can I try something else? Do you have any ideas?
Best regards, Marcin
|
|
|
Post by spannernick on Mar 20, 2021 11:07:22 GMT
Looks like you need too wipe the nand and copy the nand back, that if the nand is not damaged.
|
|
|
Post by spannernick on Mar 20, 2021 11:49:47 GMT
Look here to copy the nand image back to the Nand on THEC64 Mini, you will need to know what nand it uses too, there are 3 versions of THEC64 Mini(NTSC = ATO, PAL Silver Label = TOSHIBA, and PAL embossed Label, part of the case = ESMT.) thec64community.online/thread/567/backup-restore-firmware
|
|
|
Post by jj0 on Mar 20, 2021 13:33:52 GMT
Hello, I received recently broken c64mini. Because I hate to just throw away broken things I'm trying to repair it. So I connected USB-UART to onboard UART and this is output: HELLO! BOOT0 is starting!
boot0 version : 3.0.0
6dram size =25
ERROR! block 2 doesn't store head of Boot1 copy.
ERROR! block 3 doesn't store head of Boot1 copy.
ERROR! block 4 doesn't store head of Boot1 copy.
ERROR! block 5 doesn't store head of Boot1 copy.
ERROR! block 6 doesn't store head of Boot1 copy.
ERROR! block 7 doesn't store head of Boot1 copy.
nand block 8 is bad
nand block 9 is bad
nand block 10 is bad
Can't find a good Boot1 copy in nand.
Ready to quit "load_Boot1_from_nand".
Ready to disable icache.
Jump to Fel. So I thought: "ok, nand looks like is bad, but maybe I'll be able to start FEL recovery and try to repair NAND with nand_rw". But after runningvboot.cmd from C64Mini-FEL-boot-v1.1 I got: U-Boot SPL 2018.05-jj_0+ (Dec 21 2018 - 20:27:20 +0100)
DRAM: 0 MiB
CPU: 912000000Hz, AXI/AHB/APB: 3/2/2
Trying to boot from FEL ... and that's it. I stuck here. What worries me is "DRAM: 0 MiB". Is that's what is supposed to be when running boot.cmd? I suppose that BOOT0 is also in NAND or I'm wrong? Can I try something else? Do you have any ideas? Best regards, Marcin Boot0 is in the processors BootROM (BROM) I think. It executes in SRAM that is also on the processor. The fact that it can't load an image from NAND and also that the u-boot SPL in FEL mode shows 0 MiB DRAM (though Boot0 shows 'dram size =256') is a bit worrying, Do you know what happened to the Mini, any info from the previous owner?
|
|