Hi all.
I have a proof of concept driver code. It is mostly launcher/checker based on FSMC.
Code is currently placed under FSMCv1 directory. All function names started with stm32_ preffix.
Any suggestions?
FSMC SRAM
Moderator: RoccoMarco
Re: FSMC SRAM
Hi barthess,
As LCDs are used this way I am VERY interested into this driver. I'll take a look within the following days for sure! Furthermore, I deal with external SRAM a lot (as you might guess from my waveform generator)
~ Tectu
As LCDs are used this way I am VERY interested into this driver. I'll take a look within the following days for sure! Furthermore, I deal with external SRAM a lot (as you might guess from my waveform generator)
~ Tectu
- Giovanni
- Site Admin
- Posts: 14892
- Joined: Wed May 27, 2009 8:48 am
- Has thanked: 1202 times
- Been thanked: 996 times
Re: FSMC SRAM
Platform drivers symbols should be prefixed with the peripheral name, in this case fsmc.
Giovanni
Giovanni
Re: FSMC SRAM
Initial commits done in trunk.
What about exporting special sections for external SRAM via linker script?
@Tectu:
I need your suggestions about API.
What about exporting special sections for external SRAM via linker script?
@Tectu:
I need your suggestions about API.
- Giovanni
- Site Admin
- Posts: 14892
- Joined: Wed May 27, 2009 8:48 am
- Has thanked: 1202 times
- Been thanked: 996 times
Re: FSMC SRAM
I plan adding more memory areas to linker scripts, I need to decide on a general way to do this because I want uniformity among ports.
BTW the naming convention should be fsmcSomething() not fsmc_something, it is an API. Macros would be FSMC_SOMETHING.
Giovanni
BTW the naming convention should be fsmcSomething() not fsmc_something, it is an API. Macros would be FSMC_SOMETHING.
Giovanni