Soft 404
Rumour has it that a lot of i2c slave devices have 8051 silicon in them, that runs the i2c client state machine.
The 8051 takes little silicon space. Most manufacturers already have their i2c client state machine code ready and optimised, only to adapt it to the particular IC and burn it into OTP memory. And no more patents/licenses to pay.
Good call. I note that Silicon Labs offer a dev board which costs about the same as a Pico...
I recently purchased one of these boards from WIZnet, with the daft idea of hooking it up to a Pico and then using PIO to handle the parallel comms to hopefully eek out better performance than what SPI has to offer. Maybe that would make a good combo when attached to a RPI-W for high speed Ethernet (IPv6) data transfers etc,
scottiebabe you have my sympathy, I hate Python, any flavor. Its functionality similar to C but it has no ; and the stupid insanity of spacing, If somebody ever fixes the dam thing maybe I would use it.
Right, the indentation errors are quite common in Python. Also for embedded system it is not that great considering debugging possibilities in C.
LOL. Try using another persons Python code... just one mis-indent within a nested if statement and all sorts of chaos and destruction unfolds... I also shudder to think of how many hidden horrors lurk within complex python code for those obscure logic edge cases... because code happily runs until it needs to enter that error prone (untested) edge case.