Re: [microblaze-uclinux] strange problem with flatfsd

[John Williams <jwilliams@xxxxxxxxxxxxxx>]

Hi Eugnio,

eugenio wrote:

> The card boots ok but I have a problem with flatfsd, it always says that there 
> is no valid data in the partition. U-boot writes the flash correctly so I 
> don't know what happens with flatfsd. I also have sent SIGUSR1 signal to the 
> process but when I reboot the flash is not written.
> Am I missing anything?
> ah, my kernel didn't compile because it was lacking a const 
> CONFIG_XILINX_FLASH_WIDTH that EDK 8.1 doesn't put in the file 
> auto-config.in.

The BSP scripts distributed with PetaLinux do create these parameers.  I 
think the issue here is that the S3E-1600 reference design (downloaded 
rfom PetaLogix.com?) has a local /bsp subdir with a standalone copy of 
these tools. That snapshot is out of data and so does not create the 
WISDTH and DATAWIDTH_MATCHING params.  I will fix that up - thanks for 
finding it.

> So I put it by hand but not sure if it is correct:
> define_int CONFIG_XILINX_FLASH_WIDTH 8
> define_int CONFIG_XILINX_FLASH_DATAWIDTH_MATCHING 1

Yep, that looks ok


> physmap_auto flash device: 1000000 at 21000000
> physmap_auto probing buswidth 1
> cfi_cmdset_0001: Erase suspend on write enabled
> 0: offset=0x0,size=0x20000,blocks=128
> Using buffer write method
> physmap_auto: Using Command Line partition definition
> Creating 5 MTD partitions on "Physically mapped flash":
> 0x00000000-0x00040000 : "boot"
> 0x00040000-0x00080000 : "bootenv"
> 0x00080000-0x000c0000 : "config"
> 0x000c0000-0x004c0000 : "image"
> 0x004c0000-0x00fc0000 : "spare"
> uclinux[mtd]: RAM probe address=0x220d3a3c size=0x1d3000
> uclinux[mtd]: root filesystem index=6

> MicroBlaze auto-config flash probe(0x21000000,8388608,4): 800000 at 21000000

This is a problem - you have both the physmap_auto and mb_auto MTD 
mapping drivers enabled (as well as the generic uclinux, which is correcT)l.

You should disable the mb-auto map - and use just physmap_auto.

> flatfsd: invalid header magic
> flatfsd: Nonexistent or bad flatfs (-183), creating new one...
> flatfsd: Wrote 232 bytes to flash in 2 seconds
> flatfsd: Created 4 configuration files (124 bytes)

These messages are typically seen the first time flatfsd starts up, when 
the /dev/flash/config partition is empty (or contains old/bad data). 
flatfsd should erase the partition, and populate it with the default 
data (from /etc/default).

Do you see this message on subsequent boots?

you can also run at the command line "flatfsd -s" to trigger a save of 
the current contents from /etc/config into the flash - does that work 
for you?

Regards,

John
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/