Hi Phil,
On Tue, Apr 1, 2008 at 1:56 PM, Phil Wilshire <[EMAIL PROTECTED]> wrote:
> Hi Bob .. again
>
> If you see partitions in
> cat /proc/mtd
> or
> cat /proc/partitions
>
> then you can mainly ignore the last email.
Okay, this is what my system gives me:
/> cat /proc/mtd
dev: size erasesize name
mtd0: 002c1000 00001000 "ROMfs"
/> cat /proc/partitions
major minor #blocks name
31 0 2820 mtdblock0
But now what? For example, I tried these:
/> erase mtd0
File open error
/> erase /proc/mtd0
File open error
/> erase /dev/mtd0
File open error
/> erase mtdblock0
File open error
/> erase /proc/mtdblock0
File open error
/> erase /dev/mtdblock0
File open error
For some reason, I wasn't surprised that none of these worked. I feel
I'm missing something important...
>
> The actual entries in /dev are normally made in the
>
> vendors/<VENDOR>/<TARGET>/Makefile.
That is what I thought. So am I to guess that I need to put something
in this Makefile to create a /dev/mtd0 (for example) entry? And if
I'm right, then what would this look like?
FWIW - I am using a custom BSP that is almost exactly the
vendors/Freescale/M5329EVB port.
>
> Some architectures like the Blackfin have a
> device_table.txt
> file to specify the /dev entries.
>
> Some later , more advanced, systems may create then automatically.
>
> It's fun unraveling all of this (joke).
;-) Yeah, isn't it!
Take care,
-Bob
P.S. Don't know if you remember a colleague of mine (Jim Francis) - he
took a course from you several years ago when we were both at Payload
Systems...
>
> Regards
>
>
> Phil Wilshire
> SDCS
>
>
>
> Bob Grimes wrote:
> > On Tue, Apr 1, 2008 at 9:42 AM, Phil Wilshire <[EMAIL PROTECTED]> wrote:
> >> Hi Bob,
> >> Use eraseall to erase the entire partition
> >>
> >> eraseall /dev/mtdx
> >>
> >> Then use cp to write to the flash.
> >>
> >> cp /var/myimage /dev/mtdx
> >
> > Oh, that certainly sounds easy enough! But...
> >
> >> Where x is the kernel image partition.
> >
> > I don't have _any_ /dev/mtdx entries. How do I create these?
> >
> > Thanks!
> > -Bob
> >> Phil Wilshire
> >> SDCS
> >>
> >>
> >>
> >> Bob Grimes wrote:
> >> > My client wants the ability to upload a new image, and write it into
> >> > boot NOR flash. We have uBoot, but in many deployments, neither the
> >> > serial port nor Ethernet will be available, so we can't use uBoot to
> >> > do this. We have the basic idea of uploading (over USB Gadget serial)
> >> > a new image, storing it into RAM, then writing over the old uClinux
> >> > image (yeah, the inherent danger with power loss is an acceptable
> >> > risk). I think I (might) have the configuration options right, but
> >> > I'm not able to figure out how to do the flash write. Here are what I
> >> > _think_ are the relevant options:
> >> >
> >> > MTD=y
> >> > MTD_CFI=y
> >> > MTD_PHYSMAP=y
> >> > MTD_UCLINUX=y (Not sure if this is relevant or not...)
> >> >
> >> > I also have the memory map options set correctly.
> >> >
> >> > Now I would think I could use flashw to do the dirty work, right?
> >> >
> >> > But, I don't know how to set up the required <rom-device> argument for
> >> > flashw. I suspect I need to define a "device node" in the /dev
> >> > directory, but this is where my knowledge ends. I really don't
> >> > understand how that is done - can anyone help?
> >> >
> >> > TIA
> >> > =Bob
> >> > _______________________________________________
> >> > uClinux-dev mailing list
> >> > uClinux-dev@uclinux.org
> >> > http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
> >> > This message was resent by uclinux-dev@uclinux.org
> >> > To unsubscribe see:
> >> > http://mailman.uclinux.org/mailman/options/uclinux-dev
> >> >
> >>
> >> _______________________________________________
> >> uClinux-dev mailing list
> >> uClinux-dev@uclinux.org
> >> http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
> >> This message was resent by uclinux-dev@uclinux.org
> >> To unsubscribe see:
> >> http://mailman.uclinux.org/mailman/options/uclinux-dev
> >>
> > _______________________________________________
> > uClinux-dev mailing list
> > uClinux-dev@uclinux.org
> > http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
> > This message was resent by uclinux-dev@uclinux.org
> > To unsubscribe see:
> > http://mailman.uclinux.org/mailman/options/uclinux-dev
> >
>
> _______________________________________________
> uClinux-dev mailing list
> uClinux-dev@uclinux.org
> http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
> This message was resent by uclinux-dev@uclinux.org
> To unsubscribe see:
> http://mailman.uclinux.org/mailman/options/uclinux-dev
>
_______________________________________________
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
