[U-Boot] Problems flashing kernel

[U-Boot] Problems flashing kernel

[Kristoffer Ericson]

Greetings,

Im having issues making flashing work on my platform.
Earlier it responded that flash was not erased, but after
doing :
HP Jornada# erase 0x00080000 0x03BFFFFF
it worked.

When I do:
HP Jornada# cp.b 0xC00080000 0x00080000 1296996 (<- my kernel size)
Copy to flash... . (and just sits there)

I tried to increase the timeout defines but it still uses exact same
timeout (4096ms erase, 2ms buffer-write-timeout, 1ms write-timeout).

Chip is being reported as:
Bank # 1: CFI conformant FLASH (32 x 16) Size: 64MB in 259 Sectors
Intel Extended command set, Manufacturer ID:0x89, Device ID:0x19
Erase timeout: 4096ms, write timeout:1ms
Buffer write timeout: 2ms, buffer size: 64 bytes

Best wishes
Kristoffer

[U-Boot] Problems flashing kernel

[Stefano Babic]

Kristoffer Ericson wrote:
> Greetings,
> 

Hi,

> When I do:
> HP Jornada# cp.b 0xC00080000 0x00080000 1296996 (<- my kernel size)
> Copy to flash... . (and just sits there)

u-boot uses hexadecimal as default and you do not need to use the 0x
notation. however, 1296996 is interpreted as hexadecimal (more as 18MB).
Try with 13CA64, if your size was intended as decimal as I think.

Best regards,
Stefano Babic

-- 
=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
=====================================================================

[U-Boot] Problems flashing kernel

[Kristoffer Ericson]

On Tue, Jun 08, 2010 at 03:05:44PM +0200, Stefano Babic wrote:
> Kristoffer Ericson wrote:
> > Greetings,
> > 
> 
> Hi,
> 
> > When I do:
> > HP Jornada# cp.b 0xC00080000 0x00080000 1296996 (<- my kernel size)
> > Copy to flash... . (and just sits there)
> 
> u-boot uses hexadecimal as default and you do not need to use the 0x
> notation. however, 1296996 is interpreted as hexadecimal (more as 18MB).
> Try with 13CA64, if your size was intended as decimal as I think.

You are quite correct in that, thx. that also explains why it
took a good while longer than usual.

I cannot seem to shake the "Flash not Erased" problem though. Was thinking
to increase timeout of erase/write but they dont change even when I change
the CONFIG_SYS_FLASH_WRITE_TOUT. Any thoughts on that?

> 
> Best regards,
> Stefano Babic
> 
> -- 
> =====================================================================
> DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
> =====================================================================

[U-Boot] Problems flashing kernel

[Stefano Babic]

Kristoffer Ericson wrote:

> You are quite correct in that, thx. that also explains why it
> took a good while longer than usual.
> 
> I cannot seem to shake the "Flash not Erased" problem though. Was thinking
> to increase timeout of erase/write but they dont change even when I change
> the CONFIG_SYS_FLASH_WRITE_TOUT. Any thoughts on that?

CONFIG_SYS_FLASH_WRITE_TOUT is used on some board specific driver, but
not by the CFI driver. It seems you are using the CFI driver and you
probably can drop this CONFIG_ switch.
However, I have not understood from you previous message when the flash
has not been erased. You say that an erase command for quite the whole
flash (from 512KB to the end of the flash, as CFI reports 64MB) works.
Do you try to erase the flash to store only the kernel ? Something like
"erase 0x80000 +13CA64" ?

Best regards,
Stefano Babic

-- 
=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
=====================================================================

[U-Boot] Problems flashing kernel

[Kristoffer Ericson]

On Tue, Jun 08, 2010 at 04:31:15PM +0200, Stefano Babic wrote:
> Kristoffer Ericson wrote:
> 
> > You are quite correct in that, thx. that also explains why it
> > took a good while longer than usual.
> > 
> > I cannot seem to shake the "Flash not Erased" problem though. Was thinking
> > to increase timeout of erase/write but they dont change even when I change
> > the CONFIG_SYS_FLASH_WRITE_TOUT. Any thoughts on that?
> 
> CONFIG_SYS_FLASH_WRITE_TOUT is used on some board specific driver, but
> not by the CFI driver. It seems you are using the CFI driver and you
> probably can drop this CONFIG_ switch.

Oki, that explains it.

> However, I have not understood from you previous message when the flash
> has not been erased. You say that an erase command for quite the whole
> flash (from 512KB to the end of the flash, as CFI reports 64MB) works.
> Do you try to erase the flash to store only the kernel ? Something like
> "erase 0x80000 +13CA64" ?
> 

It worked earlier for unknown reasons, but no longer does. It has
only worked once. Erasing all the flash (aside from first 512kb) works without any error messages, but when trying to flash it still insists that
the flash is not erased. Looking with md also seems to confirm that (data found).

I must be missing something.

> Best regards,
> Stefano Babic
> 
> -- 
> =====================================================================
> DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
> =====================================================================

[U-Boot] Problems flashing kernel

[Stefano Babic]

Kristoffer Ericson wrote:

> It worked earlier for unknown reasons, but no longer does. It has 
> only worked once. Erasing all the flash (aside from first 512kb)
> works without any error messages, but when trying to flash it still
> insists that the flash is not erased. Looking with md also seems to
> confirm that (data found).

Maybe it has nothing with your problem, but because you have Intel flash
it could be possible you need to send the Unlock sequence. Have you
tried setting CONFIG_SYS_FLASH_PROTECTION ?

Best regards,
Stefano Babic

-- 
=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
=====================================================================

[U-Boot] Problems flashing kernel

[Kristoffer Ericson]

On Tue, Jun 08, 2010 at 05:01:05PM +0200, Stefano Babic wrote:
> Kristoffer Ericson wrote:
> 
> > It worked earlier for unknown reasons, but no longer does. It has 
> > only worked once. Erasing all the flash (aside from first 512kb)
> > works without any error messages, but when trying to flash it still
> > insists that the flash is not erased. Looking with md also seems to
> > confirm that (data found).
> 
> Maybe it has nothing with your problem, but because you have Intel flash
> it could be possible you need to send the Unlock sequence. Have you
> tried setting CONFIG_SYS_FLASH_PROTECTION ?

I already have it set:
#define	CONFIG_SYS_FLASH_PROTECTION	1
I just figured it was an auto-protect flash setting. Is that correct?
Should I try it without?
> 
> Best regards,
> Stefano Babic
> 
> -- 
> =====================================================================
> DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
> =====================================================================

[U-Boot] Problems flashing kernel

[Kristoffer Ericson]

On Tue, Jun 08, 2010 at 05:01:05PM +0200, Stefano Babic wrote:
> Kristoffer Ericson wrote:
> 
> > It worked earlier for unknown reasons, but no longer does. It has 
> > only worked once. Erasing all the flash (aside from first 512kb)
> > works without any error messages, but when trying to flash it still
> > insists that the flash is not erased. Looking with md also seems to
> > confirm that (data found).
> 
> Maybe it has nothing with your problem, but because you have Intel flash
> it could be possible you need to send the Unlock sequence. Have you
> tried setting CONFIG_SYS_FLASH_PROTECTION ?

I noticed something atleast inside the old bootloader (blob)
and also the kernel. It seems to add enable/disable routines for
the flash by setting PPSR |= PPC_LDD7 (on), PPSR &= ~PPC_LDD7 (off).

> 
> Best regards,
> Stefano Babic
> 
> -- 
> =====================================================================
> DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
> =====================================================================