use of devf-generic

We have an Intel 28F320J5 part on our board (ppcbe, custom). The physical
location is at 0xff000000. I’ve tried running devf-generic as follows:

devf-generic -s0xff000000 -vvvvv

The following output is given:
calloc /src/lib/fs-flash/start.c, 51: 0x80
calloc /src/lib/fs-flash/start.c, 100: 0x3c
calloc /src/lib/fs-flash/start.c, 143: 0x2c
calloc /src/lib/fs-flash/start.c, 175: 0x40
calloc /src/lib/fs-flash/start.c, 195: 0x98
devf: fs0 socket generic

trying device width = 1

devf: bus width = 1
devf: trying chip inter = 1

Nothing shows up under /dev.

What am I doing wrong?

tia

Issam

Issam Haddad <ihaddad@asurent.com> wrote:

We have an Intel 28F320J5 part on our board (ppcbe, custom). The physical
location is at 0xff000000. I’ve tried running devf-generic as follows:

devf-generic -s0xff000000 -vvvvv

It should finish by either identifying a flash device, or failing to do so.
If it does neither, it’s likely because you haven’t specified a flash size:

devf-generic -s0xff000000,0x400000 -vvvvv


The following output is given:
calloc /src/lib/fs-flash/start.c, 51: 0x80
calloc /src/lib/fs-flash/start.c, 100: 0x3c
calloc /src/lib/fs-flash/start.c, 143: 0x2c
calloc /src/lib/fs-flash/start.c, 175: 0x40
calloc /src/lib/fs-flash/start.c, 195: 0x98
devf: fs0 socket generic

trying device width = 1

devf: bus width = 1
devf: trying chip inter = 1

Nothing shows up under /dev.

What am I doing wrong?

tia

Issam


Dave Green (dgreen@qnx.com)

QNX Software Systems Ltd.
http://www.qnx.com

Specifying the size gives me the same result.

“Dave Green” <dgreen@qnx.com> wrote in message
news:a8aa8s$e5$1@nntp.qnx.com

Issam Haddad <> ihaddad@asurent.com> > wrote:
We have an Intel 28F320J5 part on our board (ppcbe, custom). The
physical
location is at 0xff000000. I’ve tried running devf-generic as follows:

devf-generic -s0xff000000 -vvvvv

It should finish by either identifying a flash device, or failing to do
so.
If it does neither, it’s likely because you haven’t specified a flash
size:

devf-generic -s0xff000000,0x400000 -vvvvv


The following output is given:
calloc /src/lib/fs-flash/start.c, 51: 0x80
calloc /src/lib/fs-flash/start.c, 100: 0x3c
calloc /src/lib/fs-flash/start.c, 143: 0x2c
calloc /src/lib/fs-flash/start.c, 175: 0x40
calloc /src/lib/fs-flash/start.c, 195: 0x98
devf: fs0 socket generic

trying device width = 1

devf: bus width = 1
devf: trying chip inter = 1

Nothing shows up under /dev.

What am I doing wrong?

tia

Issam

\

Dave Green (> dgreen@qnx.com> )

QNX Software Systems Ltd.
http://www.qnx.com

Hi,

perhaps I had the same problem on our ppc405 board.
If you add " &" to your commandline, you should see an exeption.
(Something like pagefault)

I found a bug in the flash library. (socket_option.c)
The parser of the commandline used “strtol” to convert the “-s” option.
=> If you have a flash-address with bit 31 set, like yours, you get into
trouble.
I had to change the “strtol” to “strtoul” in socket_option.c .

Michael


Issam Haddad wrote:

Specifying the size gives me the same result.

“Dave Green” <> dgreen@qnx.com> > wrote in message
news:a8aa8s$e5$> 1@nntp.qnx.com> …
Issam Haddad <> ihaddad@asurent.com> > wrote:
We have an Intel 28F320J5 part on our board (ppcbe, custom). The
physical
location is at 0xff000000. I’ve tried running devf-generic as follows:

devf-generic -s0xff000000 -vvvvv

It should finish by either identifying a flash device, or failing to do
so.
If it does neither, it’s likely because you haven’t specified a flash
size:

devf-generic -s0xff000000,0x400000 -vvvvv


The following output is given:
calloc /src/lib/fs-flash/start.c, 51: 0x80
calloc /src/lib/fs-flash/start.c, 100: 0x3c
calloc /src/lib/fs-flash/start.c, 143: 0x2c
calloc /src/lib/fs-flash/start.c, 175: 0x40
calloc /src/lib/fs-flash/start.c, 195: 0x98
devf: fs0 socket generic

trying device width = 1

devf: bus width = 1
devf: trying chip inter = 1

Nothing shows up under /dev.

What am I doing wrong?

tia

Issam

\

Dave Green (> dgreen@qnx.com> )

QNX Software Systems Ltd.
http://www.qnx.com

That would do it… Thanks for the tip. Unfortunately, since my bsp does
not include the code to devf-generic, I’ll have to write a devf- driver for
the part we’re using (not that that should be too difficult).

(I also just checked the “fixes” section on the qnx web site just in
case…).

“Michael Tasche” <michael.tasche@esd-electronics.com> wrote in message
news:3CA99B3F.7AB884AB@esd-electronics.com

Hi,

perhaps I had the same problem on our ppc405 board.
If you add " &" to your commandline, you should see an exeption.
(Something like pagefault)

I found a bug in the flash library. (socket_option.c)
The parser of the commandline used “strtol” to convert the “-s” option.
=> If you have a flash-address with bit 31 set, like yours, you get into
trouble.
I had to change the “strtol” to “strtoul” in socket_option.c .

Michael


Issam Haddad wrote:

Specifying the size gives me the same result.

“Dave Green” <> dgreen@qnx.com> > wrote in message
news:a8aa8s$e5$> 1@nntp.qnx.com> …
Issam Haddad <> ihaddad@asurent.com> > wrote:
We have an Intel 28F320J5 part on our board (ppcbe, custom). The
physical
location is at 0xff000000. I’ve tried running devf-generic as
follows:

devf-generic -s0xff000000 -vvvvv

It should finish by either identifying a flash device, or failing to
do
so.
If it does neither, it’s likely because you haven’t specified a flash
size:

devf-generic -s0xff000000,0x400000 -vvvvv


The following output is given:
calloc /src/lib/fs-flash/start.c, 51: 0x80
calloc /src/lib/fs-flash/start.c, 100: 0x3c
calloc /src/lib/fs-flash/start.c, 143: 0x2c
calloc /src/lib/fs-flash/start.c, 175: 0x40
calloc /src/lib/fs-flash/start.c, 195: 0x98
devf: fs0 socket generic

trying device width = 1

devf: bus width = 1
devf: trying chip inter = 1

Nothing shows up under /dev.

What am I doing wrong?

tia

Issam

\

Dave Green (> dgreen@qnx.com> )

QNX Software Systems Ltd.
http://www.qnx.com