Caanoo / WIZ :( Have I Bricked My Wiz?!

[glossywhite]

I just booted my Wiz (serial cable attached) and held down the right button, assuming the recovery firmware was on my SD card... but it wasn't. This is the readout I got from my terminal on the computer - looks worrying:

U-Boot 1.1.6 (Jun 10 2009 - 18:05:46)

U-Boot code: 03680000 -> 036B0AF0  BSS: -> 036E4148
RAM Configuration:
Bank #0: 00000000 64 MB
manufacture ID = 191lx
device ID = 9051lx
flash_protect ON: from 0x80000000 to 0x80030AEF
protect on 0
protect on 1
protect on 2
protect on 3
flash_protect ON: from 0x80050000 to 0x8005FFFF
protect on 5
Flash:  4 MB
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
SD ver 2.0 

SD found : Size = 1955840 KBytes  
sdmmc_SetClock.531: MES_ASSERT error
MES_SDHC_SetOutputClockDivider.1183: MES_ASSERT error
ERROR : MES_SDCARD_ReadSectors -MES_SDHC_INT_DTO count = 512
ERROR : MES_SDCARD_ReadSectors -MES_SDHC_INT_DTO fifocount = 0
ERROR : MES_SDCARD_ReadSectors dwReadSize = 512, D.TRCBCNT = 0
ERROR : MES_SDCARD_ReadSectors dwReadSize = 512, D.TRFBCNT = 0
sdi_command error
sd_read error
### main_loop entered: bootdelay=0

BOOT UPDATE ----------------------------
sdi_command error

** Unable to use mmc 0:1 for fatload **
2 : g_filesize 0
polluxb Update 1 0x4000 
Un-Protect Flash Sectors 0-5 in Bank # 1
Erase Flash Sectors 0-5 in Bank # 1 
Erasing sector 80000000
Erasing sector 80010000
Erasing sector 80020000
Erasing sector 80030000
Erasing sector 80040000
Erasing sector 80050000
 done
Copy to Flash...-done
KERNEL UPDATE ----------------------------
sdi_command error

** Unable to use mmc 0:1 for fatload **
2 : g_filesize 0
uImage Update 1 0x4000 
Un-Protect Flash Sectors 6-63 in Bank # 1
Erase Flash Sectors 6-63 in Bank # 1 
Erasing sector 80060000
Erasing sector 80070000
Erasing sector 80080000
Erasing sector 80090000
Erasing sector 800a0000
Erasing sector 800b0000
Erasing sector 800c0000
Erasing sector 800d0000
Erasing sector 800e0000
Erasing sector 800f0000
Erasing sector 80100000
Erasing sector 80110000
Erasing sector 80120000
Erasing sector 80130000
Erasing sector 80140000
Erasing sector 80150000
Erasing sector 80160000
Erasing sector 80170000
Erasing sector 80180000
Erasing sector 80190000
Erasing sector 801a0000
Erasing sector 801b0000
Erasing sector 801c0000
Erasing sector 801d0000
Erasing sector 801e0000
Erasing sector 801f0000
Erasing sector 80200000
Erasing sector 80210000
Erasing sector 80220000
Erasing sector 80230000
Erasing sector 80240000
Erasing sector 80250000
Erasing sector 80260000
Erasing sector 80270000
Erasing sector 80280000
Erasing sector 80290000
Erasing sector 802a0000
Erasing sector 802b0000
Erasing sector 802c0000
Erasing sector 802d0000
Erasing sector 802e0000
Erasing sector 802f0000
Erasing sector 80300000
Erasing sector 80310000
Erasing sector 80320000
Erasing sector 80330000
Erasing sector 80340000
Erasing sector 80350000
Erasing sector 80360000
Erasing sector 80370000
Erasing sector 80380000
Erasing sector 80390000
Erasing sector 803a0000
Erasing sector 803b0000
Erasing sector 803c0000
Erasing sector 803d0000
Erasing sector 803e0000
Erasing sector 803f0000
 done
Copy to Flash...-done
PATCH KERNEL LOAD ----------------------------
sdi_command error

** Unable to use mmc 0:1 for fatload **
2 : g_filesize 0
UPDATE RAMDISK LOAD ----------------------------
sdi_command error

** Unable to use mmc 0:1 for fatload **
2 : g_filesize 0
### main_loop: bootcmd="bootm 0x02000000"
Hit any key to stop autoboot:  0 
Bad Magic Number
gpollux# ls
Unknown command 'ls' - try 'help'
gpollux# help
?       - alias for 'help'
base    - print or set address offset
bdinfo  - print Board Info structure
bootm   - boot application image from memory
cmp     - memory compare
cp      - memory copy
crc32   - checksum calculation
erase   - erase FLASH memory
fatinfo - print information about filesystem
fatload - load binary file from a dos filesystem
fatls   - list files in a directory (default /)
flinfo  - print FLASH memory information
go      - start application at address 'addr'
help    - print online help
iminfo  - print header information for application image
loadb   - load binary file over serial line (kermit mode)
loady   - load binary file over serial line (ymodem mode)
loop    - infinite loop on address range
md      - memory display
mm      - memory modify (auto-incrementing)
mmcinit - init mmc card
mtest   - simple RAM test
mw      - memory write (fill)
nm      - memory modify (constant address)
printenv- print environment variables
protect - enable or disable FLASH write protection
reset   - Perform RESET of the CPU
run     - run commands in an environment variable
saveenv - save environment variables to persistent storage
setenv  - set environment variables
version - print monitor version
gpollux# bdinfo
arch_number = 0x0000079E
env_t       = 0x00000000
boot_params = 0x00000100
DRAM bank   = 0x00000000
-> start    = 0x00000000
-> size     = 0x04000000
ethaddr     = 11:00:33:22:55:44
ip_addr     = 192.168.0.100
baudrate    = 115200 bps
gpollux# cd /mnt
Unknown command 'cd' - try 'help'
gpollux# exit
Unknown command 'exit' - try 'help'
gpollux# reboot
Unknown command 'reboot' - try 'help'
gpollux# help
?       - alias for 'help'
base    - print or set address offset
bdinfo  - print Board Info structure
bootm   - boot application image from memory
cmp     - memory compare
cp      - memory copy
crc32   - checksum calculation
erase   - erase FLASH memory
fatinfo - print information about filesystem
fatload - load binary file from a dos filesystem
fatls   - list files in a directory (default /)
flinfo  - print FLASH memory information
go      - start application at address 'addr'
help    - print online help
iminfo  - print header information for application image
loadb   - load binary file over serial line (kermit mode)
loady   - load binary file over serial line (ymodem mode)
loop    - infinite loop on address range
md      - memory display
mm      - memory modify (auto-incrementing)
mmcinit - init mmc card
mtest   - simple RAM test
mw      - memory write (fill)
nm      - memory modify (constant address)
printenv- print environment variables
protect - enable or disable FLASH write protection
reset   - Perform RESET of the CPU
run     - run commands in an environment variable
saveenv - save environment variables to persistent storage
setenv  - set environment variables
version - print monitor version
gpollux# version

Have I bricked it?. It comes on now, but only a black screen


[EDIT]

YES!!!!!!!!!!!!!!! I UNBRICKED IT!!!... I'll tell you how tomorrow, when I wake up!!! (worked it out ALONE!)

Unbricking guide HERE: click

 

[pseudonym404]

If you're still getting the uboot prompt on the serial line, you should still be able to flash new firmware.

If you're not, the bootloader is toast... You could have a go at getting JTAG working, although as far as I'm aware nobody has tried it yet.

If you're up for that, I'd start with OpenOCD. should at least be able to get it talking to the CPU, although it might take some coding to get NAND writing working.

 

[glossywhite]

If you're still getting the uboot prompt on the serial line, you should still be able to flash new firmware.

If you're not, the bootloader is toast... You could have a go at getting JTAG working, although as far as I'm aware nobody has tried it yet.

If you're up for that, I'd start with OpenOCD. should at least be able to get it talking to the CPU, although it might take some coding to get NAND writing working.

I started it up with serial connected... nothing!. I should never have rebooted it when it was at the U-boot prompt!

 

[Claude]

Don't worry! As long the hardware isn't damaged you can always unbrick the Wiz. The Pollux processor has an Uart-Boot feature, I did the same thing on the Didj (link in my signature).
I haven't got the necessary files for the Wiz atm , but I'm sure I have them at home. So when you already have an serial cable and you are willing to void your Wiz's warranty I think I can help you.

 

[glossywhite]

Don't worry! As long the hardware isn't damaged you can always unbrick the Wiz. The Pollux processor has an Uart-Boot feature, I did the same thing on the Didj (link in my signature).
I haven't got the necessary files for the Wiz atm , but I'm sure I have them at home. So when you already have an serial cable and you are willing to void your Wiz's warranty I think I can help you.

I have a serial cable yes - you're very kind... so what do I do then? (once I have the files)

 

[Exophase]

It's enough to set serial, you have to change boot mode configuration pins too. These are also inputs over the cable, so you don't have to mod the Wiz, but you do have to know where they are and what to set them to.

I have the files that were posted here, ie the UART loader interface, boot code, and flasher code. The flasher doesn't work for me, the other things do. So I can't unbrick my Wiz with what has been provided, we need a working NAND flasher module.

glossywhite, boot it again and see if you still get the same boot message. Because it erased U-Boot - if it didn't succeed in rewriting it then you're in the same situation I'm in. If it did then you can rig an update over U-Boot, even if you have to do so manually. But it looks like you could have other problems preventing you from successfully accessing SD or something.

If it's getting SD card errors it really should not be proceeding with the update process, including erasing its bootloader. Sigh.

 

[glossywhite]

It's enough to set serial, you have to change boot mode configuration pins too. These are also inputs over the cable, so you don't have to mod the Wiz, but you do have to know where they are and what to set them to.

I have the files that were posted here, ie the UART loader interface, boot code, and flasher code. The flasher doesn't work for me, the other things do. So I can't unbrick my Wiz with what has been provided, we need a working NAND flasher module.

glossywhite, boot it again and see if you still get the same boot message. Because it erased U-Boot - if it didn't succeed in rewriting it then you're in the same situation I'm in. If it did then you can rig an update over U-Boot, even if you have to do so manually. But it looks like you could have other problems preventing you from successfully accessing SD or something.

If it's getting SD card errors it really should not be proceeding with the update process, including erasing its bootloader. Sigh.

I managed to get u-boot working without flashing it to NAND - but I have NO idea what commands I need to use to restore my proper bootloader or OS - can you help?!. Also, how long does it take to write the bootloader back to NAND (option 4) seems to take AGES!!

 

[pseudonym404]

I've so far only been loading kernels directly into ram to boot them, like this:

mmcinit
fatload mmc 0 0x02000000 uImage
bootm 0x02000000

You can obviously change the filename (uImage) to load any file, and I think you should be able to substitute an appropriate address for fatload to write to nand instead, see if the output of 'flinfo' is any help.

I've been unable to get loadb (kermit over serial line) to work at all.

 

[glossywhite]

I've so far only been loading kernels directly into ram to boot them, like this:

mmcinit
fatload mmc 0 0x02000000 uImage
bootm 0x02000000

You can obviously change the filename (uImage) to load any file, and I think you should be able to substitute an appropriate address for fatload to write to nand instead, see if the output of 'flinfo' is any help.

I've been unable to get loadb (kermit over serial line) to work at all.

Is yours bricked?. I'll tell you how to fix it tomorrow!

 

[Claude]

Glad you did it ! How about putting a "Unbrick your Wiz" tutorial / file set together?
I'm happy to help you , as you can see English is not my native language but maybe I can help you with some technical details (resistors,pins,u-boot commands and stuff).

 

[pseudonym404]

I've so far only been loading kernels directly into ram to boot them, like this:

mmcinit
fatload mmc 0 0x02000000 uImage
bootm 0x02000000

You can obviously change the filename (uImage) to load any file, and I think you should be able to substitute an appropriate address for fatload to write to nand instead, see if the output of 'flinfo' is any help.

I've been unable to get loadb (kermit over serial line) to work at all.

Is yours bricked?. I'll tell you how to fix it tomorrow!

No, still got stock firmware, just playing about with kernel stuff. I'm interested anyway though.

 

[glossywhite]

Glad you did it ! How about putting a "Unbrick your Wiz" tutorial / file set together?
I'm happy to help you , as you can see English is not my native language but maybe I can help you with some technical details (resistors,pins,u-boot commands and stuff).

I'll try to get a guide put together today. Thanks for the offer of help, but as I said, I've got all the info I need and I worked it out myself (apart from the resistors/boot pin locations which Claude helped with). I am an electronics engineer - soldering & hardware doesn't phase me, unlike a lot of software geeks .

Thanks for the offer - appreciated!.