STM32F37x, USB, Endpoints and their toggle bits

[Workalot]

I'm not alone in my confusion I think, when taking in the information of RM0313, rev6, page 838. And that is how to handle the 't' (toggle bits) in the EP registers.

Where RM0313 mentions that read-modify-write is be avoided, I see in ST's code (and others), through the many perverse #define(s), that that very thing happens.

Could the take on this be that an r-m-w cycle is necessary, but care must be taken to adjust the temporary variable (used on the read) to clear those 't ' bits not involved (so they won't be toggled), before writing the variable back?

Further, about set/clr of involved 't' bit(s). To set a 't' bit is must be at the cleared state, conversely, to clear a 't ' bit it must be at the set state.

And may I take this opportunity to mention RM0313 rev 6, sec 29.6.2, page 843. The text has the word 'address' which I feel sure is not reflective. It should be 'offset'

Workalot

[Workalot]

Got there, finally! I have a working CDC VCP. Must mention JW's...

>However, the device-only USB in STM32 is a somewhat lower-level implementation, where STATUS phase of handhsake is to be performed "manually".

... that bit of information puzzled me initially, how does one determine when and where does the Status Stage appear/occur. Nevertheless, thoughts come into focus, trials and tribulations exercised, and et voila!

Workalot is happy to share his results - I can post the module if there is interest.

[Workalot]

  "He programmed, he debugged, and did it again

  Advances were slow yet he strived to maintain

  A learned STM32 soul would see as watcher

  That Workalot's fate was sealed by a gotcha."

Had hoped the STM32F37x could be part of a set of MCUs I implement for control applications.

Its all to do with the placement in memory of the GPIO module. JW elsewhere made this clear.

Workalot

[waclawek.jan]

What's the issue?

JW

 I have a question how could CTR_RX and CTR_TX co-exist? Is not USB a half-duplex data I/O stream? That is, request/response in a lockstep arrangement.:thumbs_up::thumbs_up:

[waclawek.jan]

> Is not USB a half-duplex data I/O stream?

As I've said above:

> No. Endpoints are simplex and mutually independent. Or, from the horse's mouth:

I believe the rest that post above explains why the common misconception for "lockstep" (I wonder where this comes from, it must be a common source, I've heard this expression too many times in this context).

JW

[Workalot]

I implement bit-banding in my digital I/O application. The STM32F37x's GPIO module is located at 0x48000000, well outside of the 1MB bit-banding space.

While the F37x manual confirms that bit-banding is supported, it didn't go as far to mention the GPIO isn't. And of course, I didn't go looking - that is the gotcha.

[waclawek.jan]

Oh I see. Yes, a gotcha indeed.

You are probably aware of the GPIO_BSRR register which provides (through a mechanism different to bitbanding and local to the GPIO module) a perfect atomic write to individual output bits in GPIO_ODR. It does not provide individual-bit-addressability nor atomic access to other GPIO registers, though.

JW

[Workalot]

Yes, indeed I am aware of BSRR. STM, Atmel (Microchip) and others do the atomic write only thing as a matter of course.

And on your 'lockstep' comment: I had my UART mindset about when I posed the question. A very thing that Jan Axelson makes advice on.

While the result failed to please, the journey was pleasant. Mostly from JW's edification, thank you for taking the time.

Workalot

[Workalot]

JS

Not sure what you are referring to. If it is about the STM32F37x's USB peripheral and its endpoint representation in silicon I can say that I have my USB/VCP coded to use EP1 as interrupt IN and EP2 for Rx/Tx.

I did mention how other code I have reviewed implement EP2 as an Tx and EP3 as an Rx (maybe it was vice versa) which I suggest was all to do with avoiding Tx interrupt handling when within the Rx handler.

But on another note, a ta da!

Workalot's previous grief on a gotcha has proven to be premature, all wasn't as bad as it seemed. Taking a break from the project had me realize (when I was about 400km away) that the lack of bit-banding of the GPIO can be handled through IDR and BSRR (JW) accesses.

So the STM32F37x is now happily included in a small family of demo platforms.

Must say, weight for age the STM32F37x is a likeable MCU.