Filesystem mounting/layout

[Matthew J Fletcher]

Replying to myself.

memset'ing the SRAM area to be used to 0xff fixed it.

Once i have both RFS/SRAM and RFS/NOR filesystems up and running i will
post the code to this list i've never complete example of either.

- Matthew.


On 13 March 2013 13:50, Matthew J Fletcher <amimjf at gmail.com> wrote:

> Hi,
>
> Thanks for your help, i've got quite far now. I am upto calling
> rtems_rfs_format on my SRAM device /dev/nvda, i get an error in
> rtems_nvdisk_read_block() because the crc returned from
> rtems_nvdisk_read_checksum does not match the checksum calculated in
> rtems_nvdisk_page_checksum().
>
> The callstack is as shown.
>
> rtems_nvdisk_error() at nvdisk.c:247 0x8118bc3a
> rtems_nvdisk_read_block() at nvdisk.c:518 0x8118bdfa
> rtems_nvdisk_read() at nvdisk.c:596 0x8118bdfa
> rtems_nvdisk_ioctl() at nvdisk.c:720 0x8118bdfa
> rtems_bdbuf_execute_transfer_request() at bdbuf.c:1,976 0x8118e922
> rtems_bdbuf_read() at bdbuf.c:2,058 0x8118f3fc
> rtems_rfs_buffer_bdbuf_request() at rtems-rfs-buffer-bdbuf.c:46
> 0x811a2b70
> rtems_rfs_buffer_handle_request() at rtems-rfs-buffer.c:167 0x81198df2
> rtems_rfs_bitmap_load_map() at rtems-rfs-bitmaps.c:156 0x81197daa
> rtems_rfs_bitmap_load_map() at rtems-rfs-bitmaps.c:146 0x81197daa
> rtems_rfs_bitmap_create_search() at rtems-rfs-bitmaps.c:565 0x811981e0
> rtems_rfs_bitmap_open() at rtems-rfs-bitmaps.c:638 0x81198284
> rtems_rfs_write_group() at rtems-rfs-format.c:241 0x8118c60e
> rtems_rfs_format() at rtems-rfs-format.c:622 0x8118c60e
>
> It looks like there has not been a write yet to place a CRC on the
> filesystem, as rtems_nvdisk_write() has never been called.
>
> Do i have to issue an ioctrl() to erase the disk first ? i can see there
> is code checking if the crc is 0xffff and memset'ing the block.
>
> - Matthew
>
>
> On 13 March 2013 07:37, Sebastian Huber <
> sebastian.huber at embedded-brains.de> wrote:
>
>> On 03/12/2013 01:00 PM, Matthew J Fletcher wrote:
>>
>>> As an open question, although NOR flash is random access, would you use
>>> the
>>> SRAM alike nvdisk block driver or the flashdisk.c NOR/NAND driver ?
>>> Flashdisk
>>> seems to have more understanding of flash types, need to erase etc, and
>>> the
>>> libchip\am29lv160.c seems a generic device level NOR driver.
>>>
>>
>> For a NOR flash disk driver you may have a look at the flashdisk01 test:
>>
>> http://git.rtems.org/rtems/**tree/testsuites/libtests/**
>> flashdisk01/init.c<http://git.rtems.org/rtems/tree/testsuites/libtests/flashdisk01/init.c>
>>
>>
>> --
>> Sebastian Huber, embedded brains GmbH
>>
>> Address : Dornierstr. 4, D-82178 Puchheim, Germany
>> Phone   : +49 89 189 47 41-16
>> Fax     : +49 89 189 47 41-09
>> E-Mail  : sebastian.huber at embedded-**brains.de<sebastian.huber at embedded-brains.de>
>> PGP     : Public key available on request.
>>
>> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
>>
>
>
>
> --
>
> regards
> ---
> Matthew J Fletcher
>
>


-- 

regards
---
Matthew J Fletcher
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20130313/23104c3d/attachment-0001.html>