By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
464,775 Members | 1,132 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 464,775 IT Pros & Developers. It's quick & easy.

Linux(debian) on ARM, MTD partition

Plater
Expert 5K+
P: 7,872
I've run into a bit of trouble on this, not sure anyone here has ever done anything similar.
We have a cirus ARM chip with an MTD FLASH chip
Redboot is running on it (with ethernet support)
Partitions on flash have been made for Ramdisk and zImage.
We can successfully boot into the linux kernal and a shell.
Linux reports 8 MTD block devices (mtd0 - mtd7)
A number of them are "unallocated".
We wish to create a write-able file system in those unallocated spaces (ext2, jfss2, fat32, whatever)
However, since it's an MTD, we cannot use FDISK to partition the unallocated space.
We have found no MTD-related way to mark that unallocated space for something usefull.
Expand|Select|Wrap|Line Numbers
  1. flash_erase -j /dev/mtd3  
  2.  
Erased the mtd3 partition (which was, and still IS, marked as unallocated) with an extra erase for jfss2 support.

Has anyone ever dealt with this? Currently, there is no write-able filesystems on the device since the allocated and mounted partitions are all created from the image/ramdisk files.
Do we need to setup a filesystem in redboot for one of the unallocated sections before we boot the kernel or something?
May 16 '08 #1
Share this Question
Share on Google+
1 Reply

Plater
Expert 5K+
P: 7,872
As an update, we changed over to that jfss2 filesystem.
Using Redboot we were able to "load in" a jfss2 filesystem in place of Ramdisk/zImage combination.
The result produced a single writeable filesystem that persists through powerfailures and reboots.
It still takes a full 15secs to reboot unfortunatly so more work is needed.
May 19 '08 #2

Post your reply

Sign in to post your reply or Sign up for a free account.