Quote:
Originally Posted by SiriusHardware
I have a Pico too but haven't done much with it as I would rather programme it in 'C'- they haven't got the working environment for that language set up very well yet, although there is a script which sets everything up on the (Linux Computer) Pi if you don't mind using that as your main development machine. I really wish they had not used the 'Raspberry Pi' brand name for the Pico. The Arduino IDE is supposed to be bringing in support for the Pico as well as a few other PCBs which will use the same microcontroller.
My impression (unconfirmed) is that the Pico has quite a lot of onboard RAM and is also very fast so you could do something like the MK2 Arduino version (which currently uses an external SRAM as a serial buffer) but try using the internal RAM on the Pico instead.
If just not having the right optocouplers is an issue for Mark, fear not, I can easily populate the opto positions (if desired) by soldering SMD versions to the through hole pads on the upper side of the PCB - wouldn't add much to the weight and I have more than enough of them lying around at work.
|
The pico micropython interpreter also maps unused flash memory as a file system (about 1600k) which holds the python code you write but also can hold data files (like mk14 hex files,,,,) so you could make a mini standalone "program disk" device. I believe you can "partition" the flash like this when using C too.
I agree that it would have been less confusing to have branded it the Raspberry Pico without the "pi".