View previous topic :: View next topic |
Author |
Message |
andys
Joined: 23 Oct 2006 Posts: 175
|
M25p40 driver |
Posted: Wed Jul 11, 2012 7:45 pm |
|
|
At the link http://www.ccsinfo.com/forum/viewtopic.php?t=28445
PCM programmer said that the driver of 68hc68r2 is able to use for the m25p20.
I would like to ask if someone know any driver which is able to be used instead of m25p40 or how to modify 68hc68r2 to be used for the m25p40 component????
I would need to read from adc and use spi for writing to m25p40 memory. |
|
|
temtronic
Joined: 01 Jul 2010 Posts: 9243 Location: Greensville,Ontario
|
|
Posted: Thu Jul 12, 2012 5:32 am |
|
|
I way I read that post, PCM pgmr didn't say it would work, the OP said it did....
however without real chips I can't test the driver.
As well, you don't say which PIC you're using,compiler version,etc. All of which is necessary to help you.
hth
jay |
|
|
andys
Joined: 23 Oct 2006 Posts: 175
|
M25p40 driver |
Posted: Thu Jul 12, 2012 6:36 am |
|
|
I used dspic33fj128gp708 .
(How to find the compiler version?) |
|
|
temtronic
Joined: 01 Jul 2010 Posts: 9243 Location: Greensville,Ontario
|
|
Posted: Thu Jul 12, 2012 6:56 am |
|
|
Easy....open up the listing(ie:programfilename.lst), it'll be on the first few lines(ie: version 4.nnn). |
|
|
andys
Joined: 23 Oct 2006 Posts: 175
|
M25p40 driver |
Posted: Thu Jul 12, 2012 7:16 am |
|
|
version: 4.3.0.218
Can you help me? |
|
|
andys
Joined: 23 Oct 2006 Posts: 175
|
M25p40 driver |
Posted: Thu Jul 12, 2012 3:01 pm |
|
|
No respond yet? |
|
|
temtronic
Joined: 01 Jul 2010 Posts: 9243 Location: Greensville,Ontario
|
|
Posted: Thu Jul 12, 2012 3:45 pm |
|
|
You should printout the datasheets for of the devices and compare the communications information (SPI..timings...commands..etc.)
Then make a copy of the driver(do NOT alter the original driver !) and edit it to conform to the commands and timings for your device.
Then try it out on real devices.Be sure to store 'known' data, say 1-2-3 and be sure you can read it back !
Once you're sure this test data is correct, proceed with more testing, say 50-100 'known' data and confirm it is correct.
You might want to google your chip and PIC C driver code or similar to see if you get any 'hits'.
I do not write drivers without having the real hardware in my PIC test boards. |
|
|
|