Fabien Royer

Hi Seattle Food Geek,

I just notice that the order of the calls is incorrect:

[*][color=rgb(0,0,0);]daq[/color][color=rgb(102,102,0);].[/color][color=rgb(102,0,102);]FatFs[/color][color=rgb(102,102,0);].[/color][color=rgb(102,0,102);]CloseFile[/color][color=rgb(102,102,0);]([/color][color=rgb(0,0,0);]fileId[/color][color=rgb(102,102,0);]);[/color]
[*][color=rgb(102,0,102);]Debug[/color][color=rgb(102,102,0);].[/color][color=rgb(102,0,102);]Print[/color][color=rgb(102,102,0);]([/color][color=rgb(0,136,0);]"file closed"[/color][color=rgb(102,102,0);]);[/color]
[*][color=rgb(0,0,0);]daq[/color][color=rgb(102,102,0);].[/color][color=rgb(102,0,102);]FatFs[/color][color=rgb(102,102,0);].[/color][color=rgb(102,0,102);]SyncFile[/color][color=rgb(102,102,0);]([/color][color=rgb(0,0,0);]fileId[/color][color=rgb(102,102,0);]);[/color]
[/list]

Closing the file invalidates the fileId, and it should not be used afterward.

[color=rgb(102,102,0);font-size:14px;]Just call SyncFile() before closing the file and things should be OK [/color]

 

I hope this helps.

 

-Fabien.

[font="arial, sans-serif;font-size:12.800000190734863px;"]Hi Asbjorn,[/font]

Chris,

"[color=rgb(40,40,40);font-family:helvetica, arial, sans-serif;font-size:14px;]I'm guessing that 10.5 mbps was too fast for the module. That's a lot of data for a 48MHz microcontroller to handle that's also updating a display...so 5.25 mbps seems totally reasonable"[/color]

[color=rgb(40,40,40);font-family:helvetica, arial, sans-serif;font-size:14px;]You guessed wrong.[/color]

• [color=rgb(40,40,40);font-family:helvetica, arial, sans-serif;font-size:14px;]The Touch Display module runs on a [/color]STM32F205RET6 [color=rgb(40,40,40);font-family:helvetica, arial, sans-serif;font-size:14px;]at 120 Mhz.[/color]
• [color=rgb(40,40,40);font-family:helvetica, arial, sans-serif;font-size:14px;]The DAQ module runs on a [/color]STM32F051R8T6 at 48 MHz.

In both cases, the processing work that they perform is independent of the SPI communication throughput because it's buffered and asynchronous. A simple examination of our SPI over DMA source code would have avoid a misleading statement.

For the record, throughput has never been an issue with our modules until GoBus introduced SPI handling changes. 

Thanks Asbjorn

Interesting about the cart / navigation issue you bumped into...

Can you email me @ fabien <at> nwazet <dot> com and let me know how we can improve things? I'd love your feedback.

Cheers,

-Fabien.