About MNels

MNels · 2019-01-02

We're seeing what looks like an extra or spurious read from the QSPI block on our STM32F765BI. As yet, we're not able to pinpoint the cause and could use some ideas of where else to look. Sorry that this gets a bit long. Background:We're using the...

MNels · 2019-02-08

Thanks Amel!!Mike

MNels · 2019-02-07

Hi Chead1...,I can't begin to express enough thanks for your comments. I've worked with ARM and ST for quite a few years and I'll have to admit your note put a new wrinkle in my forehead. When JW first mentioned this I tried blocking the memory map...

MNels · 2019-01-23

Hi Amel,Thanks for the pointers. As I read back through my original post, it's definitely not as clear as it seemed when I wrote it. A summary of the problem would be: An EEPROM read restarts without an explicit FW write to the QSPI block re...

MNels · 2019-01-04

Hi JW,Thanks for the response. There are some really good ideas in your list. As a follow up, we've implemented the 'read chip status register' work around and downloaded 40GB worth of log files (ran all night) with out a hiccup. Point by point..,....

User statistics

User Activity

Help with odd STM32F765BI QSPI behavior? We're seeing what looks like an extra or spurious read transaction.

Re: Help with odd STM32F765BI QSPI behavior? We're seeing what looks like an extra or spurious read transaction.

Re: Help with odd STM32F765BI QSPI behavior? We're seeing what looks like an extra or spurious read transaction.

Re: Help with odd STM32F765BI QSPI behavior? We're seeing what looks like an extra or spurious read transaction.

Re: Help with odd STM32F765BI QSPI behavior? We're seeing what looks like an extra or spurious read transaction.