Thread: [Flashforth-devel] SPI FRAM memory drivers
Brought to you by:
oh2aun
From: om1zz <om...@vo...> - 2015-05-24 17:32:50
|
Hi, at https://github.com/igor-m/flashforth/tree/master/examples are examples of SPI drivers for FRAM SPI memory (byte, word, double access) working with dspic33fjgp128/pic24 etc. It is a quick hack to see how the stuff works, and it works. Needs to be optimised a bit however, asm must be used where applicable in order to speed the stuff up. My memories are over 64kB so they have got 3 bytes long address. Currently there is a block number (64kB per block) and an address within 64kB. Mind you have to care about proper alignment as the address step is 1 or 2 or 4 for above types. More in sources. Igor. |
From: om1zz <om...@vo...> - 2015-05-26 08:41:09
|
Hi, much more optimized code there. WR/RD bytes, words, doubles and quads into/from FRAM, speeds up to 300kB/sec with quads at 27MHz Fcy. I may try with my magnetic MRAMs, but a microscope needed for the soldering job :) Igor ______________________________________________________________ > Od: om1zz <om...@vo...> > Komu: "flashforth-devel" <fla...@li...> > Datum: 24.05.2015 19:33 > Předmět: [Flashforth-devel] SPI FRAM memory drivers > >Hi, at >https://github.com/igor-m/flashforth/tree/master/examples >are examples of SPI drivers for FRAM SPI memory (byte, word, double access) working with dspic33fjgp128/pic24 etc. >It is a quick hack to see how the stuff works, and it works. >Needs to be optimised a bit however, asm must be used where applicable in order to speed the stuff up. >My memories are over 64kB so they have got 3 bytes long address. Currently there is a block number (64kB per block) and an address within 64kB. Mind you have to care about proper alignment as the address step is 1 or 2 or 4 for above types. >More in sources. >Igor. > >------------------------------------------------------------------------------ >One dashboard for servers and applications across Physical-Virtual-Cloud >Widest out-of-the-box monitoring support with 50+ applications >Performance metrics, stats and reports that give you Actionable Insights >Deep dive visibility with transaction tracing using APM Insight. >http://ad.doubleclick.net/ddm/clk/290420510;117567292;y >_______________________________________________ >Flashforth-devel mailing list >Fla...@li... >https://lists.sourceforge.net/lists/listinfo/flashforth-devel > |
From: om1zz <om...@vo...> - 2015-05-27 17:36:24
|
Hi, there is a new driver for magnetoresistive MRAM (Everspin) MR25H40, 512kBytes, 8pin. Together with below FRAM (Ramtron, now Cypress) this is a great solution when you require a nonvolatile external 8pin SPI memory with up to 40/50Mhz SPI clock and write such fast as read (no write delays like eeprom/flash, no page buffers). Unlimited endurance. Could be used as a standard SPI sram, but nonvolatile (no external backup battery needed). Now we need a tiny filesystem written in forth :) Igor ______________________________________________________________ > Od: "om1zz" <om...@vo...> > Komu: "flashforth-devel" <fla...@li...> > Datum: 26.05.2015 10:40 > Předmět: Re: [Flashforth-devel] SPI FRAM memory drivers > >Hi, much more optimized code there. WR/RD bytes, words, doubles and quads into/from FRAM, speeds up to 300kB/sec with quads at 27MHz Fcy. I may try with my magnetic MRAMs, but a microscope needed for the soldering job :) >Igor > >______________________________________________________________ >> Od: om1zz <om...@vo...> >> Komu: "flashforth-devel" <fla...@li...> >> Datum: 24.05.2015 19:33 >> Předmět: [Flashforth-devel] SPI FRAM memory drivers >> >>Hi, at >>https://github.com/igor-m/flashforth/tree/master/examples >>are examples of SPI drivers for FRAM SPI memory (byte, word, double access) working with dspic33fjgp128/pic24 etc. >>It is a quick hack to see how the stuff works, and it works. >>Needs to be optimised a bit however, asm must be used where applicable in order to speed the stuff up. >>My memories are over 64kB so they have got 3 bytes long address. Currently there is a block number (64kB per block) and an address within 64kB. Mind you have to care about proper alignment as the address step is 1 or 2 or 4 for above types. >>More in sources. >>Igor. >> >>------------------------------------------------------------------------------ >>One dashboard for servers and applications across Physical-Virtual-Cloud >>Widest out-of-the-box monitoring support with 50+ applications >>Performance metrics, stats and reports that give you Actionable Insights >>Deep dive visibility with transaction tracing using APM Insight. >>http://ad.doubleclick.net/ddm/clk/290420510;117567292;y >>_______________________________________________ >>Flashforth-devel mailing list >>Fla...@li... >>https://lists.sourceforge.net/lists/listinfo/flashforth-devel >> > |
From: om1zz <om...@vo...> - 2015-05-29 17:07:30
|
Hi, if somebody seeks a driver for popular PCF8563T RTC (with lowest backup current consuption (200nA), afaik) you may find it at: https://github.com/igor-m/EXPERIMENTAL_FF/tree/master/examples Needs an i2c low level driver, for example from PeterJ for pic24. Igor ______________________________________________________________ > Od: "om1zz" <om...@vo...> > Komu: "flashforth-devel" <fla...@li...> > Datum: 27.05.2015 19:36 > Předmět: Re: [Flashforth-devel] SPI FRAM and MRAM memory drivers > >Hi, >there is a new driver for magnetoresistive MRAM (Everspin) MR25H40, 512kBytes, 8pin. >Together with below FRAM (Ramtron, now Cypress) this is a great solution when you require a nonvolatile external 8pin SPI memory >with up to 40/50Mhz SPI clock and write such fast as read (no write delays like eeprom/flash, no page buffers). >Unlimited endurance. >Could be used as a standard SPI sram, but nonvolatile (no external backup battery needed). >Now we need a tiny filesystem written in forth :) >Igor > |