I try to run the flash file system driver supplied with the BSP on the
Samsung SMDK2410 development board with :
devf-generic -s 0x10000,64k
(which is a valid block in the AM29LV800 flash) but I get a SIGSEGV.
Am I doing something wrong or is the flash file system not ported properly
in this beta ?
Nick,
I’m going to assume that your flash part is not 64k in size, but has 64k
block sizes.
Try using this command (assuming your flash part is 32M in size and has
a block size of 64k):
devf-generic -s0x10000,32M,64k
Nick Horsley wrote:
I try to run the flash file system driver supplied with the BSP on the
Samsung SMDK2410 development board with :devf-generic -s 0x10000,64k
(which is a valid block in the AM29LV800 flash) but I get a SIGSEGV.
Am I doing something wrong or is the flash file system not ported properly
in this beta ?
Nick Horsley <nick.horsley@emsgroup.co.uk> wrote:
I try to run the flash file system driver supplied with the BSP on the
Samsung SMDK2410 development board with :devf-generic -s 0x10000,64k
(which is a valid block in the AM29LV800 flash) but I get a SIGSEGV.
Am I doing something wrong or is the flash file system not ported properly
in this beta ?
Trying to force the flash driver to recognize less flash than is actually
present likely will not work. As the flash driver probes the flash, it
will report back what it finds, not just what’s specified on the command
line.
Depending on what you’re trying to achieve, I’d recommend that you
start the flash driver as normal, and then use the flashctl utility
to create a single 64k partition, and work with that partition. For
example, assuming your board as 32M of flash, starting at address 0:
devf-generic -s0,32M
flashctl -p/dev/fs0p0 -o64k -l64k -evf
then, slay and restart the driver, and you’ll have a /fs0p0 which
should be 64k in size. Note that since the flash driver requires
at least one spare block to use as an erase block, this partition
will likely be read-only.
How much flash do you have on board in total, and what is your
intended layout of data on the flash?
–
David Green (dgreen@qnx.com)
QNX Software Systems Ltd.
http://www.qnx.com
There is just 1MB of flash currently fitted (at address 0). This is divided
into 64kB blocks except the first 4 blocks (where the monitor is located)
which are 16kB, 8kB, 8kB and 32KB respectively. I want all but the first
64kB available to the flash file system.
“Dave Green” <dgreen@qnx.com> wrote in message
news:c82ofu$bil$1@inn.qnx.com…
Nick Horsley <> nick.horsley@emsgroup.co.uk> > wrote:
I try to run the flash file system driver supplied with the BSP on the
Samsung SMDK2410 development board with :devf-generic -s 0x10000,64k
(which is a valid block in the AM29LV800 flash) but I get a SIGSEGV.
Am I doing something wrong or is the flash file system not ported
properly
in this beta ?Trying to force the flash driver to recognize less flash than is actually
present likely will not work. As the flash driver probes the flash, it
will report back what it finds, not just what’s specified on the command
line.Depending on what you’re trying to achieve, I’d recommend that you
start the flash driver as normal, and then use the flashctl utility
to create a single 64k partition, and work with that partition. For
example, assuming your board as 32M of flash, starting at address 0:devf-generic -s0,32M
flashctl -p/dev/fs0p0 -o64k -l64k -evf
then, slay and restart the driver, and you’ll have a /fs0p0 which
should be 64k in size. Note that since the flash driver requires
at least one spare block to use as an erase block, this partition
will likely be read-only.How much flash do you have on board in total, and what is your
intended layout of data on the flash?–
David Green (> dgreen@qnx.com> )
QNX Software Systems Ltd.
http://www.qnx.com
Nick Horsley <nick.horsley@emsgroup.co.uk> wrote:
There is just 1MB of flash currently fitted (at address 0). This is divided
into 64kB blocks except the first 4 blocks (where the monitor is located)
which are 16kB, 8kB, 8kB and 32KB respectively. I want all but the first
64kB available to the flash file system.
To achieve this, you would do the following:
devf-generic -s0,1M
flashctl -p/dev/fs0p0 -o64k -s960k -efv
Then, slay and restart devf-generic. /fs0p0 should be present,
and have a size of 960k.
“Dave Green” <> dgreen@qnx.com> > wrote in message
news:c82ofu$bil$> 1@inn.qnx.com> …
Nick Horsley <> nick.horsley@emsgroup.co.uk> > wrote:
I try to run the flash file system driver supplied with the BSP on the
Samsung SMDK2410 development board with :devf-generic -s 0x10000,64k
(which is a valid block in the AM29LV800 flash) but I get a SIGSEGV.
Am I doing something wrong or is the flash file system not ported
properly
in this beta ?Trying to force the flash driver to recognize less flash than is actually
present likely will not work. As the flash driver probes the flash, it
will report back what it finds, not just what’s specified on the command
line.Depending on what you’re trying to achieve, I’d recommend that you
start the flash driver as normal, and then use the flashctl utility
to create a single 64k partition, and work with that partition. For
example, assuming your board as 32M of flash, starting at address 0:devf-generic -s0,32M
flashctl -p/dev/fs0p0 -o64k -l64k -evf
then, slay and restart the driver, and you’ll have a /fs0p0 which
should be 64k in size. Note that since the flash driver requires
at least one spare block to use as an erase block, this partition
will likely be read-only.How much flash do you have on board in total, and what is your
intended layout of data on the flash?–
David Green (> dgreen@qnx.com> )
QNX Software Systems Ltd.
http://www.qnx.com
–
David Green (dgreen@qnx.com)
QNX Software Systems Ltd.
http://www.qnx.com
I always get a SIGSEGV error with whatever parameters I use with
devf-generic.
“Dave Green” <dgreen@qnx.com> wrote in message
news:c8abmc$54l$1@inn.qnx.com…
Nick Horsley <> nick.horsley@emsgroup.co.uk> > wrote:
There is just 1MB of flash currently fitted (at address 0). This is
divided
into 64kB blocks except the first 4 blocks (where the monitor is
located)
which are 16kB, 8kB, 8kB and 32KB respectively. I want all but the first
64kB available to the flash file system.To achieve this, you would do the following:
devf-generic -s0,1M
flashctl -p/dev/fs0p0 -o64k -s960k -efv
Then, slay and restart devf-generic. /fs0p0 should be present,
and have a size of 960k.
“Dave Green” <> dgreen@qnx.com> > wrote in message
news:c82ofu$bil$> 1@inn.qnx.com> …
Nick Horsley <> nick.horsley@emsgroup.co.uk> > wrote:
I try to run the flash file system driver supplied with the BSP on
the
Samsung SMDK2410 development board with :devf-generic -s 0x10000,64k
(which is a valid block in the AM29LV800 flash) but I get a SIGSEGV.
Am I doing something wrong or is the flash file system not ported
properly
in this beta ?Trying to force the flash driver to recognize less flash than is
actually
present likely will not work. As the flash driver probes the flash, it
will report back what it finds, not just what’s specified on the
command
line.Depending on what you’re trying to achieve, I’d recommend that you
start the flash driver as normal, and then use the flashctl utility
to create a single 64k partition, and work with that partition. For
example, assuming your board as 32M of flash, starting at address 0:devf-generic -s0,32M
flashctl -p/dev/fs0p0 -o64k -l64k -evf
then, slay and restart the driver, and you’ll have a /fs0p0 which
should be 64k in size. Note that since the flash driver requires
at least one spare block to use as an erase block, this partition
will likely be read-only.How much flash do you have on board in total, and what is your
intended layout of data on the flash?–
David Green (> dgreen@qnx.com> )
QNX Software Systems Ltd.
http://www.qnx.com
\David Green (> dgreen@qnx.com> )
QNX Software Systems Ltd.
http://www.qnx.com
Nick Horsley <nick.horsley@emsgroup.co.uk> wrote:
I always get a SIGSEGV error with whatever parameters I use with
devf-generic.
Can you describe the current settings of J6, J7, and J9 on your
board?
“Dave Green” <> dgreen@qnx.com> > wrote in message
news:c8abmc$54l$> 1@inn.qnx.com> …
Nick Horsley <> nick.horsley@emsgroup.co.uk> > wrote:
There is just 1MB of flash currently fitted (at address 0). This is
divided
into 64kB blocks except the first 4 blocks (where the monitor is
located)
which are 16kB, 8kB, 8kB and 32KB respectively. I want all but the first
64kB available to the flash file system.To achieve this, you would do the following:
devf-generic -s0,1M
flashctl -p/dev/fs0p0 -o64k -s960k -efv
Then, slay and restart devf-generic. /fs0p0 should be present,
and have a size of 960k.
“Dave Green” <> dgreen@qnx.com> > wrote in message
news:c82ofu$bil$> 1@inn.qnx.com> …
Nick Horsley <> nick.horsley@emsgroup.co.uk> > wrote:
I try to run the flash file system driver supplied with the BSP on
the
Samsung SMDK2410 development board with :devf-generic -s 0x10000,64k
(which is a valid block in the AM29LV800 flash) but I get a SIGSEGV.
Am I doing something wrong or is the flash file system not ported
properly
in this beta ?Trying to force the flash driver to recognize less flash than is
actually
present likely will not work. As the flash driver probes the flash, it
will report back what it finds, not just what’s specified on the
command
line.Depending on what you’re trying to achieve, I’d recommend that you
start the flash driver as normal, and then use the flashctl utility
to create a single 64k partition, and work with that partition. For
example, assuming your board as 32M of flash, starting at address 0:devf-generic -s0,32M
flashctl -p/dev/fs0p0 -o64k -l64k -evf
then, slay and restart the driver, and you’ll have a /fs0p0 which
should be 64k in size. Note that since the flash driver requires
at least one spare block to use as an erase block, this partition
will likely be read-only.How much flash do you have on board in total, and what is your
intended layout of data on the flash?–
David Green (> dgreen@qnx.com> )
QNX Software Systems Ltd.
http://www.qnx.com
\David Green (> dgreen@qnx.com> )
QNX Software Systems Ltd.
http://www.qnx.com
–
David Green (dgreen@qnx.com)
QNX Software Systems Ltd.
http://www.qnx.com
These jumpers are set for 16bit AMD flash - J6 pins 2-3 connected, J9/J7
pins 1-2 connected. (The boot loader wouldn’t run if this were not the
case.)
“Dave Green” <dgreen@qnx.com> wrote in message
news:c8amse$dkr$1@inn.qnx.com…
Nick Horsley <> nick.horsley@emsgroup.co.uk> > wrote:
I always get a SIGSEGV error with whatever parameters I use with
devf-generic.Can you describe the current settings of J6, J7, and J9 on your
board?
“Dave Green” <> dgreen@qnx.com> > wrote in message
news:c8abmc$54l$> 1@inn.qnx.com> …
Nick Horsley <> nick.horsley@emsgroup.co.uk> > wrote:
There is just 1MB of flash currently fitted (at address 0). This is
divided
into 64kB blocks except the first 4 blocks (where the monitor is
located)
which are 16kB, 8kB, 8kB and 32KB respectively. I want all but the
first
64kB available to the flash file system.To achieve this, you would do the following:
devf-generic -s0,1M
flashctl -p/dev/fs0p0 -o64k -s960k -efv
Then, slay and restart devf-generic. /fs0p0 should be present,
and have a size of 960k.
“Dave Green” <> dgreen@qnx.com> > wrote in message
news:c82ofu$bil$> 1@inn.qnx.com> …
Nick Horsley <> nick.horsley@emsgroup.co.uk> > wrote:
I try to run the flash file system driver supplied with the BSP on
the
Samsung SMDK2410 development board with :devf-generic -s 0x10000,64k
(which is a valid block in the AM29LV800 flash) but I get a
SIGSEGV.Am I doing something wrong or is the flash file system not ported
properly
in this beta ?Trying to force the flash driver to recognize less flash than is
actually
present likely will not work. As the flash driver probes the flash,
it
will report back what it finds, not just what’s specified on the
command
line.Depending on what you’re trying to achieve, I’d recommend that you
start the flash driver as normal, and then use the flashctl utility
to create a single 64k partition, and work with that partition. For
example, assuming your board as 32M of flash, starting at address 0:devf-generic -s0,32M
flashctl -p/dev/fs0p0 -o64k -l64k -evf
then, slay and restart the driver, and you’ll have a /fs0p0 which
should be 64k in size. Note that since the flash driver requires
at least one spare block to use as an erase block, this partition
will likely be read-only.How much flash do you have on board in total, and what is your
intended layout of data on the flash?–
David Green (> dgreen@qnx.com> )
QNX Software Systems Ltd.
http://www.qnx.com
\David Green (> dgreen@qnx.com> )
QNX Software Systems Ltd.
http://www.qnx.com
\David Green (> dgreen@qnx.com> )
QNX Software Systems Ltd.
http://www.qnx.com
Nick Horsley <nick.horsley@emsgroup.co.uk> wrote:
These jumpers are set for 16bit AMD flash - J6 pins 2-3 connected, J9/J7
pins 1-2 connected. (The boot loader wouldn’t run if this were not the
case.)
Answered via e-mail.
“Dave Green” <> dgreen@qnx.com> > wrote in message
news:c8amse$dkr$> 1@inn.qnx.com> …
Nick Horsley <> nick.horsley@emsgroup.co.uk> > wrote:
I always get a SIGSEGV error with whatever parameters I use with
devf-generic.Can you describe the current settings of J6, J7, and J9 on your
board?
“Dave Green” <> dgreen@qnx.com> > wrote in message
news:c8abmc$54l$> 1@inn.qnx.com> …
Nick Horsley <> nick.horsley@emsgroup.co.uk> > wrote:
There is just 1MB of flash currently fitted (at address 0). This is
divided
into 64kB blocks except the first 4 blocks (where the monitor is
located)
which are 16kB, 8kB, 8kB and 32KB respectively. I want all but the
first
64kB available to the flash file system.To achieve this, you would do the following:
devf-generic -s0,1M
flashctl -p/dev/fs0p0 -o64k -s960k -efv
Then, slay and restart devf-generic. /fs0p0 should be present,
and have a size of 960k.
“Dave Green” <> dgreen@qnx.com> > wrote in message
news:c82ofu$bil$> 1@inn.qnx.com> …
Nick Horsley <> nick.horsley@emsgroup.co.uk> > wrote:
I try to run the flash file system driver supplied with the BSP on
the
Samsung SMDK2410 development board with :devf-generic -s 0x10000,64k
(which is a valid block in the AM29LV800 flash) but I get a
SIGSEGV.Am I doing something wrong or is the flash file system not ported
properly
in this beta ?Trying to force the flash driver to recognize less flash than is
actually
present likely will not work. As the flash driver probes the flash,
it
will report back what it finds, not just what’s specified on the
command
line.Depending on what you’re trying to achieve, I’d recommend that you
start the flash driver as normal, and then use the flashctl utility
to create a single 64k partition, and work with that partition. For
example, assuming your board as 32M of flash, starting at address 0:devf-generic -s0,32M
flashctl -p/dev/fs0p0 -o64k -l64k -evf
then, slay and restart the driver, and you’ll have a /fs0p0 which
should be 64k in size. Note that since the flash driver requires
at least one spare block to use as an erase block, this partition
will likely be read-only.How much flash do you have on board in total, and what is your
intended layout of data on the flash?–
David Green (> dgreen@qnx.com> )
QNX Software Systems Ltd.
http://www.qnx.com
\David Green (> dgreen@qnx.com> )
QNX Software Systems Ltd.
http://www.qnx.com
\David Green (> dgreen@qnx.com> )
QNX Software Systems Ltd.
http://www.qnx.com
–
David Green (dgreen@qnx.com)
QNX Software Systems Ltd.
http://www.qnx.com