TF CD32 Riser Revision 2 Design Complete

[arkadiusz.makarenko]

Worth noting...

Clock, reset and supply management
– 1.7 V to 3.6 V application supply and I/Os
– POR, PDR, PVD and BOR
– Dedicated USB power
– 4-to-26 MHz crystal oscillator
– Internal 16 MHz factory-trimmed RC (1%
accuracy)
– 32 kHz oscillator for RTC with calibration
– Internal 32 kHz RC with calibration

Can you use the internal 16Mhz?

I don't think it is precise enough for USB.

[terriblefire]

I don't think it is precise enough for USB.

Should be enough to prove the clock is the issue.

[arkadiusz.makarenko]

I don't think it is precise enough for USB.

Should be enough to prove the clock is the issue.

Clock is not the issue.
I am almost certain that it is config of the chip.

I have just checked HID2AMI (which did work 100% ok with f105). I swapped chip to f722 and it exactly the same story.

[terriblefire]

Clock is not the issue.
I am almost certain that it is config of the chip.

I have just checked HID2AMI (which did work 100% ok with f105). I swapped chip to f722 and it exactly the same story.

There is the STM32 Utility

[arkadiusz.makarenko]

I have ordered Nucleo f722 dev board to understand this chip better.

[terriblefire]

I have ordered Nucleo f722 dev board to understand this chip better.

Good call. Is that dev board schema available?

[arkadiusz.makarenko]

I have implemented simple blinky and what I did find.
When I clock it from internal clock it is nice steady blinking. But when I set up external clock crystal it does work, but it is disco - visible difference between led toggle.

[terriblefire]

I have implemented simple blinky and what I did find.
When I clock it from internal clock it is nice steady blinking. But when I set up external clock crystal it does work, but it is disco - visible difference between led toggle.

That is really weird. And the same on HID2AMI with the F722?

[arkadiusz.makarenko]

I have implemented simple blinky and what I did find.
When I clock it from internal clock it is nice steady blinking. But when I set up external clock crystal it does work, but it is disco - visible difference between led toggle.

That is really weird. And the same on HID2AMI with the F722?

Yes ...
but Clock Resolver is not doing right job, there must be a bug there or on code generation.
I have slowed down core to 48Mhz manually, (automatically it goes to randomly either 92Mhz or 216) and I managed to get device Ready, and so far no crashes and LED toggling nicely and steady. I need to check USB HS (I read that code generator is buggy as well enabling wrong clocks on this section)

EDIT
And I have now both USB HS and FS responding up to Ready state. :)

[terriblefire]

So clock generator code is a pile of crap? Damn if you cant trust this then....