GTA02 NAND problem and devirginator

[Leonardo Guardati]

On Wed, Oct 30, 2013 at 07:14:12AM -0400, Benjamin Deering wrote:
> I did something like this years and years ago.  I broke the screen
> on my GTA02 and SDG systems sent me a 'broken' gta02 so I could use
> the screen.  I played a little with the broken one and found that
> the bbt had almost every sector in it.
> 
> I was able to rebuild the bbt and I still use that gta02 when my
> gta04 isn't working well.
> 
> Sorry I can't remember the specifics, but I know I was able to do it
> without a debug board and almost certainly from the NOR u-boot.
> 
> I vaguely remember a u-boot option to switch console output between
> serial and USB.  If serial (debug board) isn't working for you,
> maybe try USB?
> 
> Good luck,
> 
> Ben

After some investigations I found that the display could be broken
(that is unrelated to the not booting issue).

Also I tried to find the error about usb when running the RAM
version of u-boot.


######### BEGIN console output ################

U-Boot 1.3.2-moko12 (Dec 17 2008 - 00:49:17)

I2C:   ready
DRAM:  128 MB
Flash:  2 MB
NAND:  Bad block table not found for chip 0
Bad block table not found for chip 0
256 MiB
Glamo core device ID: 0x3650, Revision 0x0002
USB:   S3C2410 USB Deviced
mtdparts variable not set, see 'help mtdparts'
mtdparts variable not set, see 'help mtdparts'
mtdparts variable not set, see 'help mtdparts'
mtdparts variable not set, see 'help mtdparts'
mtdparts variable not set, see 'help mtdparts'
mtdparts variable not set, see 'help mtdparts'
ERROR: usbd_device_event_irq(), 613: (00000000,4) NULL device or device->bus
undefined instruction
pc : [<00000004>]          lr : [<33f88bcc>]
sp : 33ed8e9c  ip : 33f88bcc     fp : 34007f3c
r10: 34007f60  r9 : 34007f68     r8 : 33edbfdc
r7 : 00000004  r6 : 00000000     r5 : 00000003  r4 : 34007d14
r3 : 00000003  r2 : 00000000     r1 : 00000003  r0 : 34007d14
Flags: nzCv  IRQs off  FIQs off  Mode SVC_32
Resetting CPU ...


######### END console output ################


The strange thing is that the first argument ( 00000000 ) means the
handler to the device is not initialized.


That could mean a problem in the usb module.