Think of all files for a project (specifications, tests, research, mechanical, electrical, software, FPGA, manufacturing, etc.) living under a single hierarchy of directories for each product or project. One of the reasons is that it breaks file and project management standards. Not the kind of thing I like to do, but it works. Like you, we always use Windows, even for the big Pi developments, but we've just had to hold our noses and put a couple of Pi4s to use for the current project.įor me running Ubuntu on a VM on Windows takes care of this. Unfortunately RP2040 Windows support is on the point of unusable. That said, documentation, so far, has been excellent. They are powerful, yes, but, at a minimum, code security is lacking. Maybe the most important comment I could make is that I am not sure I would have selected this device were it not for supply chain issues. The transition to the RP2040 was forced upon us by the supply chain, so you work with what you have, rather than what you wish you had. We are porting over from STM32 and using C/C++, but MicroPython might become attractive for other products.Īs someone else mentioned, this is an interesting new experience because most all embedded MCU decisions I have ever made tend to be based around the history of the chips, tools and favorably-licensed libraries available. For example: Do you have to release your source code if your product is coded using MicroPython? I don't know the answer to that one. To the extent that there might be important IP in there, this could be a deal-breaker.

One of the other huge concerns with the Pico ecosystem is the fact that you have to be super careful about GPL or you will find yourself having to release your source code. Coming to this from STM32, and only because the chips are unobtainable right now. That might be a deal-breaker for us in the long term. I'll know a lot more about this in the coming days.Ĭode security is important. So, I feel this might need some attention in the future. I get it that RPI is Linux-centric, but I think I can say that most hardware engineering shops tend to be Windows-centric, if anything because so many of the tools we use are on that platform. I get the sense from what someone else mentioned that Windows development support might be less-than-ideal. Still feeling my way around the chip and toolchain.

The product isn't the boards, they go into a device. Initial run will be in the order of a thousand boards. We are working on a design that will go to manufacturing in a couple of months. I am curious to know if there are any companies which have considered RP2040 as the base MCU for their products and if they have started developing on RP2040?

Siemens nx software rpi