←back to thread

700 points elipsitz | 7 comments | | HN request time: 0.001s | source | bottom
Show context
doe_eyes ◴[] No.41192510[source]
I think it's a good way to introduce these chips, and it's a great project, but the author's (frankly weird) beef with STM32H7 is detracting from the point they're trying to make:

> So, in conclusion, go replan all your STM32H7 projects with RP2350, save money, headaches, and time.

STM32H7 chips can run much faster and have a wider selection of peripherals than RP2350. RP2350 excels in some other dimensions, including the number of (heterogenous) cores. Either way, this is nowhere near apples-to-apples.

Further, they're not the only Cortex-M7 vendor, so if the conclusion is that STM32H7 sucks (it mostly doesn't), it doesn't follow that you should be instead using Cortex-M33 on RPi. You could be going with Microchip (hobbyist-friendly), NXP (preferred by many commercial buyers), or a number of lesser-known manufacturers.

replies(3): >>41192554 #>>41193627 #>>41193749 #
1. dmitrygr ◴[] No.41192554[source]
1. Nobody has a wider selection of peripherals than a chip with 3 PIOs.

2. And my beef is personal - I spent months (MONTHS of my life) debugging the damn H7, only to find a set of huge bugs in the main reason I had been trying to use it (QSPI ram support), showed it to the manufacturer, and had them do nothing. Later they came back and, without admitting i was right about the bugs, said that "another customer is seeing same issues, what was the workaround you said found?" I told them that i'll share the workaround when they admit the problem. Silence since.

I fully reserve the right to be pissy at shitty companies in public on my website!

replies(3): >>41192629 #>>41192855 #>>41194446 #
2. doe_eyes ◴[] No.41192629[source]
I'm not arguing you can't be angry with them, I'm just saying that to me, it detracts from the point about the new platform. Regarding #1, I'm sure you know that peripherals in the MCU world mean more than just digital I/O. Further, even in the digital domain, the reason PIO isn't more popular is that most people don't want to DIY complex communication protocols.
3. uticus ◴[] No.41192855[source]
[edit: I retract this, I see you’ve had secretly in your possession to play with for over a year. You lucky dog. ]

> I have been anti-recommending STM’s chips to everyone for a few years now due to STM’s behaviour with regards to the clearly-demonstrated-to-them hardware issues.

You certainly reserve the right. However it is unclear to me why the recommendation to complaints over a months-long period is a product that has just been released.

Trying to ask in a very unbiased way since as a hobbyist I’m looking into ST, Microchip, and RP2040. For my part I’ve had two out of four RP2040 come to me dead on arrival, as part of two separate boards from different vendors - one being Pi Pico from Digilent. Not a ton of experience with Microchip but I hear they have their own problems. Nobody’s perfect, the question is how do the options compare.

replies(2): >>41193800 #>>41193828 #
4. limpbizkitfan ◴[] No.41193800[source]
I don’t think the issue is QA related, ST released a chip that says it can perform X when the reality is it can not perform X.
5. naikrovek ◴[] No.41193828[source]
they're complaining now because they still feel the pain now. while writing the article, they're thinking of how things would have been different on previous projects if they had had this chip, and that is digging up pain and they felt it should be expressed.

I don't know what's so unclear. Have you never had a strong opinion about someone else's stuff? Man, I have.

6. 15155 ◴[] No.41194446[source]
> 1. Nobody has a wider selection of peripherals than a chip with 3 PIOs.

NXP FlexIO says "Hello!"

replies(1): >>41198611 #
7. spacedcowboy ◴[] No.41198611[source]
FlexIO is (I think) powerful, however... I'm not sure if it's me or the way they describe it with all the bit-serialisers/shifters interacting - but I grok the PIO assembly a damn sight easier than FlexIO.

Maybe it's just me. Maybe.