MTD traces on operation with filesystem

[Joaquim Duran]

Dear all,

My name is Joaquim Duran. We're using Linux to develop and embedded
device (linux v3.0 on an ARM device based on DM37x with flash). We've
some stability problem with the flash contents, so we would like to
trace the write operations to flash.

To print traces, we've changed the variable 'mtd_debug_verbose' to
0x7. With this configuration, we get traces when we access to the
flash when using the /dev/mtdblockX' device file, like:

dd if=uImage of=/dev/mtdblock3 bs=131072
[...]
[ 107.481018] mtdblock: write on "kernel" at 0x362c00, size 0x200
[ 107.487182] mtdblock: write on "kernel" at 0x362e00, size 0x200
[ 107.493438] mtdblock: write on "kernel" at 0x363000, size 0x200
[ 107.499664] mtdblock: write on "kernel" at 0x363200, size 0x200
[ 107.505859] mtdblock: write on "kernel" at 0x363400, size 0x200
[ 107.512084] mtdblock: write on "kernel" at 0x363600, size 0x200
[ 107.518280] mtdblock: write on "kernel" at 0x363800, size 0x200
[ 107.524475] mtdblock: write on "kernel" at 0x363a00, size 0x200
[ 107.530700] mtdblock: write on "kernel" at 0x363c00, size 0x200
[ 107.537017] mtdblock: write on "kernel" at 0x363e00, size 0x200
[ 107.543334] mtdblock: write on "kernel" at 0x364000, size 0x200
[...]

but not if I do write operation using the file system:

dd if=/dev/urandom of=test.txt bs=1024 count=4096

Maybe should I flush the MTD cache? How can I get the traces?

Thanks and Best Regards,

Joaquim Duran