BDI2000 configuration file for MPC8313E-RDB

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

Accessing 8541 registers from user space

[Charles Krinke]

I have a need to be able to read and write the gpio data registers PDATC
and PDATD from a user space program.=20

We have a userspace program that succesfully mmaps an offset in /dev/mem
and reads/writes registers in a CPLD at 0xFF00_0000.

The issue seems to be that when I mmap /dev/mem to 0xE000_0D50 to read
the PDATC register, Linux-2.6.17.11 just locks up.

Can anyone shed a little light on why this could be happening?

Charles Krinke

Re: Accessing 8541 registers from user space

[Kumar Gala]

On May 16, 2007, at 4:59 PM, Charles Krinke wrote:

> I have a need to be able to read and write the gpio data registers  
> PDATC
> and PDATD from a user space program.
>
> We have a userspace program that succesfully mmaps an offset in / 
> dev/mem
> and reads/writes registers in a CPLD at 0xFF00_0000.
>
> The issue seems to be that when I mmap /dev/mem to 0xE000_0D50 to read
> the PDATC register, Linux-2.6.17.11 just locks up.
>
> Can anyone shed a little light on why this could be happening?

One theory is you aren't reading PDATC at the right offset.  Not sure  
what happens if you read a non-existent register offset.

I'm think you want 0xe009_0d50.

- k