Lost access to M25Pxx in move to 2013.01

George Pontis GPontis at z9.com
Sat Feb 2 11:35:39 EST 2013


Under 2012.11 I created a new board support package for custom hardware,
which included a M25P32. I store barebox and its environment there, and boot
from it. The board file also defines partitions for it. The first three look
like this:

        devfs_add_partition("m25p0",        0, 0x050000,
DEVFS_PARTITION_FIXED, "barebox");
        devfs_add_partition("m25p0", 0x050000, 0x010000,
DEVFS_PARTITION_FIXED, "env0");
        devfs_add_partition("m25p0", 0x060000, 0x330000,
DEVFS_PARTITION_FIXED, "kernel");

This created devices /dev/barebox, /dev/env0, and so on. It also allowed for
simple commands like "erase /dev/barebox", "tftp barebox.bin /dev/barebox",
etc.

More recently I updated to the 2013.01 release. My config file is not much
different and it still has enabled CONFIG_MTD, CONFIG_MTD_M25P80,
CONFIG_MTD_WRITE. The new release starts up just fine and boots the kernel
as usual. However, it does not see the M25P32.

With the earlier release, I saw a line displayed at startup as so:

m25p m25p0: m25p32 (4096 Kbytes)

Also, devinfo listed the partitions on the part. That m25p line is not
displayed with the 2013.01 release and there are no partitions. Devinfo does
show one line for the m25p driver.

Any suggestions where to look for a fix ?





More information about the barebox mailing list