AW: BDI2000 configuration file for MPC8313E-RDB

AW: BDI2000 configuration file for MPC8313E-RDB

[Frank Prepelica]

Hi Leonid,

firstly, thanks for reply!

But, are you sure that I cannot access NAND memory via=20
BDI2000? Because I used BDI2000 with the MPC8343M Board=20
and there is "only" 64MB NAND memory. Thus I stored the=20
U-Boot (image was broken) into the flash memory.

Frank


-----Urspr=FCngliche Nachricht-----
Von: Leonid [mailto:Leonid@a-k-a.net]=20
Gesendet: Mittwoch, 16. Mai 2007 22:37
An: Frank Prepelica; linuxppc-embedded@ozlabs.org
Betreff: RE: BDI2000 configuration file for MPC8313E-RDB

AFAIK, BDI2000 doesn't support NAND... of course you can load some code
which has NAND support into RAM (even u-boot if compiled properly) and
thus program NAND flash. But BDI firmware cannot program NAND directly.

Leonid.

________________________________________
From: linuxppc-embedded-bounces+leonid=3Da-k-a.net@ozlabs.org
[mailto:linuxppc-embedded-bounces+leonid=3Da-k-a.net@ozlabs.org] On =
Behalf
Of Frank Prepelica
Sent: Wednesday, May 16, 2007 7:25 AM
To: linuxppc-embedded@ozlabs.org
Subject: BDI2000 configuration file for MPC8313E-RDB

Hi all,

maybe this is not the appropriate mailing list, sorry for that!

but, does anyone got a working BDI2000 configuration file + reg.
definitions for MPC8313E-RDB
to get access to NAND memory? I got one but there's only access to NOR
memory.

Many thanks in advance!

Best regards
Frank

RE: BDI2000 configuration file for MPC8313E-RDB

[Leonid]

On Thursday, May 17, 2007 11:00 PM Frank Prepelica wrote:
> Hi Leonid,
> firstly, thanks for reply!

You are very welcome.

> But, are you sure that I cannot access NAND memory via=20
> BDI2000?=20

In the first place, let me quote Ruedi Dummermuth from Abatron, BDI2000
vendor:

> > Leonid asked:
> > And here most important question comes: for our actual HW we are
going=20
> > to use ST-Micro NAND flash, one of NAND512-B, NAND01G-B, NAND02G-B,=20
> > NAND04G-B and NAND08G-B. Is BDI2000 capable of programming these=20
> > flashes? What changes in .cfg file are required?

> Sorry, but the BDI does not support programming any NAND flash.
> You can write your own driver. Then load the data and the driver into=20
> SDRAM via the BDI and execute it.

This passage also has a suggestion how you can use BDI2000 to program
NAND indirectly: load NAND-capable software to RAM.

> Because I used BDI2000 with the MPC8343M Board=20
> and there is "only" 64MB NAND memory. Thus I stored the=20
> U-Boot (image was broken) into the flash memory.

I'm afraid I didn't understand you. Are you saying that you actually
were able to program NAND using BDI2000? I would like to know how you
achieved that. I suspect that was some kind of "indirect" procedure,
Ruedi wrote about, but please provide details.

See, it's not a question that BDI2000 can be used with board which has
NAND flash on it, just it's not capable of NAND direct programming as it
does in the case of NOR flash.

I also have AMCC Sequoia board with both NOR and NAND flash. On this
board you can boot u-boot from NOR first and use it to program NAND.

Regards,

Leonid.

Re: BDI2000 configuration file for MPC8313E-RDB

[Stefan Roese]

On Friday 18 May 2007, Leonid wrote:
> See, it's not a question that BDI2000 can be used with board which has
> NAND flash on it, just it's not capable of NAND direct programming as it
> does in the case of NOR flash.

Yes, "direct" NAND programming via BDI2000 is not possible. At least not at 
the moment with the current firmware versions.

> I also have AMCC Sequoia board with both NOR and NAND flash. On this
> board you can boot u-boot from NOR first and use it to program NAND.

Correct.

Just a side note: You can also boot the Sequoia from NAND directly if you have 
programmed the NAND U-Boot version for the Sequoia, as the 440EP(x) supports 
direct NAND booting.

Best regards,
Stefan

RE: BDI2000 configuration file for MPC8313E-RDB

[Frank Prepelica]

Hi Leonid,

the PowerTAB pro JTAG Debugger cannot access NAND directly like the =
BDI2000.
I thought it could, but as you said there's no way to program NAND =
directly.

The configuration file I posted was the unmodified one that I got from =
the http://www.ultsol.com/ webpage. Therefore you find at section [FILE] =
PCB82xx120.ep. (I change the IP and the file to u-boot.bin)

I still got the problem that I don't know how to get access to NAND to
store the 4KB bootloader and to boot completely from NAND.=20

I tried via u-boot by booting from NOR.

=3D> nand info
Device 0: NAND 32MiB 3,3V 8-bit, sector size 16 KiB


=3D> nand erase=20

NAND erase: device 0 whole chip
Erasing at 0x1ffc000 -- 100% complete.
OK
=3D>


That seems each command works. (show info and erase NAND)

But when I'm trying to write for example u-boot.bin to NAND
I'll get this:
=3D> nand write.e 3000000 f8000000 29790

NAND write: device 0 offset 0xf8000000, size 0x29790


Data did not fit into device, due to bad blocks
 169872 bytes written: ERROR
=3D>

Furthermore, when I trying to display NAND memory
I'll get this:
=3D> md 0xf8000000
f8000000:Bus Fault @ 0x00000900, fixup 0x00000000
Machine check in kernel mode.
Caused by (from msr): regs 07f38cc0 Unknown values in msr
NIP: 00000900 XER: 20000000 LR: 07FD4430 REGS: 07f38cc0 TRAP: 0200 DAR: =
FFFFFFFF
MSR: 00001000 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 00

GPR00: 07FD4430 07F38DB0 00000080 00000000 B09F0000 00000010 00000001 =
00000008=20
GPR08: 00000001 00000020 00000000 00000000 07F38B78 00000000 07FFC000 =
09FBB000=20
GPR16: 00000000 00000000 00000000 00000000 07F38DB8 00000040 07F38DB8 =
07F38DB8=20
GPR24: 00000000 00000100 00000010 00000004 F8000000 07F38F5C 07FFCDA8 =
07F38DB8=20
Call backtrace:=20
07FD4430 07FDD8D8 07FDCFD0 07FDD12C 07FCCDAC 07FBFAC8 07FBE66C=20
7EB143A6=20
machine check
Resetting the board.

Why? Is the NAND memory not correctly mapped to 0xf8000000? Where
can I change the mapping?

I'm aware of that these are very basic questions, but it doesn't becomes
clear by reading the board specific manuals.=20


Best regards

Frank.





-----Urspr=FCngliche Nachricht-----
Von: Leonid [mailto:Leonid@a-k-a.net]=20
Gesendet: Montag, 21. Mai 2007 17:28
An: Frank Prepelica
Cc: linuxppc-embedded@ozlabs.org
Betreff: RE: BDI2000 configuration file for MPC8313E-RDB

On Monday, May 21, 2007 12:25 AM Frank Prepelica wrote:
> Sorry, but the BDI does not support programming any NAND flash.
> You can write your own driver. Then load the data and the driver into=20
> SDRAM via the BDI and execute it.

> Well, I think I have to try this, if there's really no other way.=20
> I'm not quite sure, maybe you know the PowerTAB Pro JTAG Debugger,
> (it's recommended in the manuals) could this one get directly access
> to NAND memory?

No, I don't but I would like to learn more about NAND flash programmers.

> Uhm, it's possible that achieved that in an "indirect" way that I was
> not aware of. But as I said, the complete flash and ram was empty,
just
> loaded=20
> the corresponding BDI config file to BDI2000 JTAG and I got access to
> flash memory where I placed the bootloader image. Hmm, anyway ;)

> The BDI config: http://www.ultsol.com/config/Emb%20Planet/83xx.cfg

It's still not clear from your description what has been done - "I got
access to flash memory" sounds too vague. It's quite possible that SW
you are using does the trick; at least you have some file, loaded from
the host to RAM:

[HOST]
IP          10.0.0.198
FILE        PCB82xx120.ep

Where did you get this PCB82xx120.ep file from?

In any rate, FLASH section of this configuration file specifies NOR
flash so it's out of question that BDI2000 could program NAND by itself:

[FLASH]
CHIPTYPE    MIRRORX16   ;Flash type: Micron Q-Flash MT28F640J3

Moreover, since workspace is disabled, direct image programming shall be
really slooow - you had to notice that. Did you? Most likely not - SW
burned your flash.


Best regards

Leonid.

RE: BDI2000 configuration file for MPC8313E-RDB

[Frank Prepelica]

> > Leonid asked:
> > And here most important question comes: for our actual HW we are
going=20
> > to use ST-Micro NAND flash, one of NAND512-B, NAND01G-B, NAND02G-B,=20
> > NAND04G-B and NAND08G-B. Is BDI2000 capable of programming these=20
> > flashes? What changes in .cfg file are required?

> Sorry, but the BDI does not support programming any NAND flash.
> You can write your own driver. Then load the data and the driver into=20
> SDRAM via the BDI and execute it.

Well, I think I have to try this, if there's really no other way.=20
I'm not quite sure, maybe you know the PowerTAB Pro JTAG Debugger,
(it's recommended in the manuals) could this one get directly access
to NAND memory?

> I'm afraid I didn't understand you. Are you saying that you actually
> were able to program NAND using BDI2000? I would like to know how you
> achieved that. I suspect that was some kind of "indirect" procedure,
> Ruedi wrote about, but please provide details.

Uhm, it's possible that achieved that in an "indirect" way that I was
not aware of. But as I said, the complete flash and ram was empty, just
loaded=20
the corresponding BDI config file to BDI2000 JTAG and I got access to
flash memory where I placed the bootloader image. Hmm, anyway ;)

The BDI config: http://www.ultsol.com/config/Emb%20Planet/83xx.cfg


Best regards

Frank

RE: BDI2000 configuration file for MPC8313E-RDB

[Leonid]

On Monday, May 21, 2007 12:25 AM Frank Prepelica wrote:
> Sorry, but the BDI does not support programming any NAND flash.
> You can write your own driver. Then load the data and the driver into=20
> SDRAM via the BDI and execute it.

> Well, I think I have to try this, if there's really no other way.=20
> I'm not quite sure, maybe you know the PowerTAB Pro JTAG Debugger,
> (it's recommended in the manuals) could this one get directly access
> to NAND memory?

No, I don't but I would like to learn more about NAND flash programmers.

> Uhm, it's possible that achieved that in an "indirect" way that I was
> not aware of. But as I said, the complete flash and ram was empty,
just
> loaded=20
> the corresponding BDI config file to BDI2000 JTAG and I got access to
> flash memory where I placed the bootloader image. Hmm, anyway ;)

> The BDI config: http://www.ultsol.com/config/Emb%20Planet/83xx.cfg

It's still not clear from your description what has been done - "I got
access to flash memory" sounds too vague. It's quite possible that SW
you are using does the trick; at least you have some file, loaded from
the host to RAM:

[HOST]
IP          10.0.0.198
FILE        PCB82xx120.ep

Where did you get this PCB82xx120.ep file from?

In any rate, FLASH section of this configuration file specifies NOR
flash so it's out of question that BDI2000 could program NAND by itself:

[FLASH]
CHIPTYPE    MIRRORX16   ;Flash type: Micron Q-Flash MT28F640J3

Moreover, since workspace is disabled, direct image programming shall be
really slooow - you had to notice that. Did you? Most likely not - SW
burned your flash.


Best regards

Leonid.

BDI2000 configuration file for MPC8313E-RDB

[Frank Prepelica]

[-- Attachment #1: Type: text/plain, Size: 336 bytes --]

Hi all,

 

maybe this is not the appropriate mailing list, sorry for that!

 

but, does anyone got a working BDI2000 configuration file + reg.
definitions for MPC8313E-RDB

to get access to NAND memory? I got one but there's only access to NOR
memory.

 

Many thanks in advance!

 

Best regards

Frank

 


[-- Attachment #2: Type: text/html, Size: 3191 bytes --]

RE: BDI2000 configuration file for MPC8313E-RDB

[Leonid]

AFAIK, BDI2000 doesn't support NAND... of course you can load some code
which has NAND support into RAM (even u-boot if compiled properly) and
thus program NAND flash. But BDI firmware cannot program NAND directly.

Leonid.

________________________________________
From: linuxppc-embedded-bounces+leonid=3Da-k-a.net@ozlabs.org
[mailto:linuxppc-embedded-bounces+leonid=3Da-k-a.net@ozlabs.org] On =
Behalf
Of Frank Prepelica
Sent: Wednesday, May 16, 2007 7:25 AM
To: linuxppc-embedded@ozlabs.org
Subject: BDI2000 configuration file for MPC8313E-RDB

Hi all,

maybe this is not the appropriate mailing list, sorry for that!

but, does anyone got a working BDI2000 configuration file + reg.
definitions for MPC8313E-RDB
to get access to NAND memory? I got one but there's only access to NOR
memory.

Many thanks in advance!

Best regards
Frank