RFS on NVRAM (RTEMS 4.10.1)

[Oleg Moroz]

all bytes should be 0xff before formatting. Because beginning of nvdisk 
is checksum area for each block in data area of NVDISK.

-------------------------
|ffff,ffff,ffff,ffff| checksums area
-------------------------
     data area
|ff,ff,ff,ff,ff,ff,ff,ff| block
|ff,ff,ff,ff,ff,ff,ff,ff| block
|ff,ff,ff,ff,ff,ff,ff,ff| block
|ff,ff,ff,ff,ff,ff,ff,ff| block
|ff,ff,ff,ff,ff,ff,ff,ff| block
|ff,ff,ff,ff,ff,ff,ff,ff| block
|ff,ff,ff,ff,ff,ff,ff,ff| block
-------------------------


checksum of block contains only 0xff  is 0xffff and nvdisk checking will 
be passed.
> Hi All,
>
> When we try to mount the RFS on a NVRAM having non 0xFF data it crashes. We cannot see any error on MMI but the CPU gives bus exception indicating the software is trying to write to a write protected location.
>
>
> We use the below configuration and have 256KB of NVRAM(actually SRAM).
>
> const rtems_nvdisk_config rtems_nvdisk_configuration[] =
> {
>    {
>      block_size:         NVRAMDISK_BLOCK_SIZE, //512
>      device_count:       1,
>      devices:&rtems_nv_heap_device_descriptor[0],
>      flags:              0,
>      info_level:         0
>    }
> };
>
> If we manually intialize the NVRAM first with 0XFF and then mount RFS it works without any problem. Can anyone please guide us how to fix this problem?
>
> Thanks&  Best Regards,
> Viral.
>
>
>
>
>
> _______________________________________________
> rtems-users mailing list
> rtems-users at rtems.org
> http://www.rtems.org/mailman/listinfo/rtems-users
>