FSMC support strategy

[gradoj]

I've added a basic FSMC module to micropython for a custom board with external SRAM. I've exposed a very simple FSMC.send and .recv. They are currently blocking calls not taking advantage of the DMA. I was thinking of taking the spi module and model the FSMC after it for consistency - a send and recv function using the DMA. Another option would be to mount the external ram or flash as another drive where the user could create files and don't expose the FSMC module to the user at all. I was wondering if any of the developers have put any thought into this or have any preference which direction would be best for Micropython? Another thought - this is the first step to getting a tft lcd drive interface for the stm32.

[dhylands]

I guess it depends on what the SRAM is going to be storing.

You could also access it directly using ustruct.

[gradoj]

In my application the send recv is all I need. I'm not exactly sure what you had in mind with ustruct. What would that look like? .pack2ram() and .unpackfrom()

[dhylands]

I'm not sure what your RAM looks like.

I think I said ustruct, and I think I meant to say uctypes.

[stick]

@gradoj is your code available somewhere?