* brucehoult braces for the avalanche of PSoC people...
Also, may be if you could tell us what exactly went wrong, we could suggest a replacement MCU.
Also, may be if you could tell us what exactly went wrong, we could suggest a replacement MCU.Well, the most recent disappointment was with the STM32F446, which has a different USB controller than the other chips in the F4xx series. Something that isn't highlighted or mentioned in the migration documents.
Sure, I could just write my own drivers, but only to a certain extent. I don't really want to write a USB stack for example.
Sure, I could just write my own drivers, but only to a certain extent. I don't really want to write a USB stack for example.so instead of writing drivers you want to write drivers and peripherals?
I don't really want to write a USB stack for example.
Well, the most recent disappointment was with the STM32F446, which has a different USB controller than the other chips in the F4xx series. Something that isn't highlighted or mentioned in the migration documents.
Another issue thats been brewing for a few years is that ST is moving over to their HAL, which, honestly, is a pile. New chips aren't supported by the old StdPeriph libraries.
Sure, I could just write my own drivers, but only to a certain extent. I don't really want to write a USB stack for example.
Another issue thats been brewing for a few years is that ST is moving over to their HAL, which, honestly, is a pile. New chips aren't supported by the old StdPeriph libraries.That is true for all vendors. Relying on vendor software support is a big mistake. Build your own software library.
Sure, I could just write my own drivers, but only to a certain extent. I don't really want to write a USB stack for example.You would have to for your own peripheral anyway. And it is not that hard to write a USB stack for simple scenarios.
Also, the biggest problem for USB in FPGA is memory. Small FPGAs don't have enough of embedded memory, and you need to have buffers for USB.
The Cypress PSoCs seem interesting, but being forced into Windows is a showstopper for me.
After recently experiencing a few disappointments with the STM32 range of MCUs, I've been looking for alternatives.
Btw, may i ask on your F446 can you change PB3,PB4 PA15 from ALT to GEN mode without losing debug interface or causing CPU to behave funny?
... Um... Why don't you just move over to the STM32F4 part that has a better USB peripheral? Or am I asking too simple of a question this late in the thread?
After recently experiencing a few disappointments with the STM32 range of MCUs, I've been looking for alternatives.A "few"? USB but what "else" is different?
Bit more on-topic: check out Microsemi Smartfusion devices.
author=stmdude link=topic=95231.msg1304750#msg1304750 date=1505764611]
On the F446, not a lot (except the USB stuff I've discovered).
The disappointments are more with the whole family of MCUs. The newer chips aren't supported with the tried-and-tested StdPeriph library (yes, I can bang the registers myself, but sometimes you just want to get the easy stuff done, quickly).
Also, their prices are pretty insane. I'm switching from the F446 to F429, which is a $12 chip (@1 qty).
I can source dual-core Cortex-A9 SoCs for $2...
ALT to "GEN"? Are you talking about changing the pin from alternate-function to regular GPIO?
If you give me a bit more info, I can try it out.
That's what I'm doing for this project. I'm moving to a F429 instead. Twice the cost, with no additional functionality that I need/want.
I'm looking into the FPGA stuff as a way to be able to spin some custom peripherals to offload the CPU when I need to talk to weird and wonderful peripherals.
The Cypress PSoCs seem interesting, but being forced into Windows is a showstopper for me.
* brucehoult braces for the avalanche of PSoC people...
https://en.wikipedia.org/wiki/PSoC
Also, their prices are pretty insane. I'm switching from the F446 to F429, which is a $12 chip (@1 qty). I can source dual-core Cortex-A9 SoCs for $2...
Yes, I don't get the point of this thread. It looks like the amount of manual work is going to increase many times with FPGA path (even if such thing existed and was practical).
Don't like HAL/Cube/wehatever? Well make your own. You will have to anyway with FPGA.
So if you are looking for simplicity, then just pick a micro and build up a code base you know and can reuse.
Yea.. OK. The STM32F429 is too expensive, so you're question is about hardcoding an ARM core an FPGA.
I don't understand why you are not seriously considering different families/architectures then.. aside the fact that you'd have to change your username then
but what does the STM32F4 have that you can't find in others so it's so difficult to switch?
I wonder if it's the 2xCAN + USB combo, i recently went for a PIC32MK for this very reason, it was the cheapest (available in a small QFN package)
but of course, i don't think this is the case.
Yes, I don't get the point of this thread. It looks like the amount of manual work is going to increase many times with FPGA path (even if such thing existed and was practical).