Adafruit Trinket M0 and CircuitPython 

Arduinos and similar boards can easily measure voltages and make decisions based on that. I'm just learning CircuitPython myself, but in C, this would be something like if(analogRead(A0)>512{foo;}else{bar;}}

Sorry about that I forget to add them to the description. Fixed now.

You can use both if you like.

It cannot run directly off of a 9 volt because the regulator can only handle up to 5v.

You are already on youtube so do a search for say LCD 'liquid crystal display ' see what comes up. "innovative" has no meaning here; everything you will see already exists. If you go to Arduino or Adafruit learn sections you will see very elaborate tutorials for there products. The last point to do this type of hobby being inquisitive is a must. In most cases when you ask a question of the host on youtube it should be about what they have presented otherwise as you can see He did not answer your request. When searching be as specific as you can.

This is probably a good starting place: circuitpython.org/libraries

Thanks for the reference. I'd looked at that before and couldn't find what I was looking for. What I found this time was the API Reference documents. I wanted to know is what all the functions were available from a specific library module. I really enjoy your channel!

@@rodproctor5466 I think what you're asking for is a combination of inspecting in realtime docs.python.org/3/library/functions.html#dir and further reference for the functions themselves github.com/adafruit/circuitpython

I call a high level of tom-foolery. No 'language' runs on a microcontroller except for binary. Last I checked: processors only used *ASM instruction sets represented by machine code and not an interpreter. The blinking-error fancy footwork is probably just the IDE flashing the LED with the error-logic defined within the software before 'converting' the un-interpreted erroneous code. ... Just my ungoogling skepticism, could be totally wrong but I have a feeling that I'm bang on. Only way to convince me otherwise is to pull the source code directly off the flash once it's been programmed.

You dont compile anything, you upload plain text files with .py extension to it by dragging and dropping the same way you would with a thumb drive and every time main.py is updated it is automatically executed

@@mikescholz6429 once you do this, and delete the files from your computer: is there any way to retrieve the .py or .pyc file from the trinket device? (If not, then that answers any question of how you program an MCU using Python... You don't 😯😜)

James S yes you can open the .py file directly from the board in a text editor, make changes and as soon as you click save it starts executing the new code. There are binary compiled libraries on the board as well that comprise the actual interpreter but your actual loop stays in plain text. Also if you get one of the boards with the M4 cortex that has like 4 times as much ram it can do some decently heavy lifting. The chip is linked to IIRC a 4mb flash memory chip that holds your code as well as bitmaps, wav files or whatever else you may need. I have a setup that plays bitmap files on addressable LED strips where each row of pixels is one frame of the length of the strip and sequentially writes each row going down the image.

@@mikescholz6429 So the MCU can't actually be programmed with Python, there's a subsystem on the chip, just like on your computer, that interprets the code and runs it on the processor. Perfect. :). Exactly as I thought. :D. Thanks for the clarification. Cool that it has removable storage!

this*

codewith.mu

Circuitpython is a derivative of micropython developed and maintained by Adafruit. It makes the language simpler and education friendly.

@@vinaybharadwaj802 Thank you, And what about libraries? Aren't they are same

@@Saketh-Chandra CircuitPython has a larger collection of libraries designed for it's hardware API that do not work directly with MicroPython.

increase the frequency of the on and off example and send it through a speaker, there you go

The link in the description.

Yup! M4 and nRF52840 boards will store and run more CircuitPython code than an M0 will (and run faster too!)

MARK!!! Bonjour!!!

Sir

*So say we all!*

really? how would the LED be powered, then, without a positive rail?

You're mostly correct but I'll have to disagree slightly. What you said is true in most of high level software development but breaks down when getting closer to the actual hardware. It makes a metric ton of difference whether you know C or python when your writing firmware/ other microcontroller code. This is due to the fact that at sufficiently low levels, the language you're writing needs to conform to the actual hardware without any abstraction layers making your life easier. It's fine and dandy blinking some LEDs with circuit python (which is actually just a sort of perverted C wrapper) but when, for example, reading data from a I2C connected sensor you really need to understand actual silicon register sizes, pointers and all sort of low level stuff that simply isn't present in python.

TR7H Fair.

The flashes are for the case where you don't have a computer handy. If a screen is attached it will show the error just like the serial output.

The point is easy access to newcommers, easier development for more complex applications and data processing. Of course the performance is 'horrible' compared to c, but let's be honest: A well programmed Arduino is more than powerful enough for almost all IoT projects, but the atmega is almost 20 years old. The ESP32 has a dual-core arm processor and tons of interfaces and hardware extentions, is cheaper than an arduino and still (running python) more powerfull than the atmega. Moore's law also applies to MCUs and it is high time for another abstraction layer. The arduino project was a milestone over 15 years ago, making MCUs accessible to makers, providing an easy to use IDE/compiler and acess via usb/uart (MCU development kits were proprietary and expensive until then). Micropython (or equivalent) even get rid of (cross-)compiling and makes testing, developing and deploying even easier. I highly recommend trying it yourself! Cheers!

Very true, graphite is conductive, and may short the wrong pins and BOOM! great video though

In your ever so humble opinion.