bak

Author: cirosantilli

ciro-santilli-s-hardware.bigb

@@ -80,6 +80,8 @@ https://www.amazon.co.uk/dp/B0CL41RG93
 
 https://www.amazon.co.uk/dp/B0B76VGXYH
 
+<MicroPython> driver: https://github.com/Danielerikrust/LCD-20x4-Feed
+
 = ELEGOO Upgraded Electronics Fun Kit
 {c}
 {parent=Electronic components}
@@ -120,10 +122,15 @@ https://www.amazon.co.uk/dp/B0B76VGXYH
 * Buttons
 * CDS-55 Photoresistor
 * Electrolytic Capacitor
-* MF52D 103f 3950 thermistor
+* Focusens MF52D 103f 3950 thermistor. Beta value 25/50 Celcius: 3950. R_25: I measured 9.61 k Ohms. The number 103 they document as:
+  * digit 1: code of dimension
+  * digit 2: rated resistance
+  * digit 3: fills with its precision symbol
+  These descriptions are weird, but ChatGPT has the theory that the first two digits are actual values, and the last is multiplier, so $10 \times 10^3$ which makes 10k.
+  but I have no idea how that maps to 10 k Ohms.
 * PN2222 General Purpose Transistor
 * Passive buzzer
-* 3386p Bourns Precision Potentiometer - 1 103T: 10 Ohms to 2 mega Ohms. TODO part broken? Multimeter measures fixed 10 kOhms no matter where I set it
+* 3386p Bourns Precision Potentiometer - 1 103T: from 0 to 10k Ohms, measured with multimeter. According to the manual the "103" mean 10 k oms, which is consistent with our measurement. "P 103" is etched into the part.
 * <LEDs>:
   * White LED 10x
   * Kingbright RGB LEDs 10x red, green, yellow, blue:

cirosantilli.github.io.code-workspace

@@ -57,6 +57,7 @@
             "Czochralski",
             "Deeptech",
             "deletionist",
+            "devboard",
             "Dietterich",
             "Disqus",
             "distro",
@@ -148,6 +149,7 @@
             "microarray",
             "microbenchmark",
             "Microbotics",
+            "Microcontroller",
             "microfilament",
             "Microtubule",
             "minicolumn",
@@ -219,6 +221,7 @@
             "Toffoli",
             "translocator",
             "Transmembrane",
+            "treshold",
             "TSMC",
             "Tuttle",
             "UCSB",

computer-hardware.bigb

@@ -1018,6 +1018,34 @@ It is interpreted. It actually implements a Python (-like ?) interpreter that ca
 
 As a result, it is both very convenient, as it does not require a C toolchain to build for, but also very slow and produces larger images.
 
+= Run MicroPython on X
+{c}
+{parent=MicroPython}
+
+= MicroPython example
+{c}
+{parent=MicroPython}
+
+Under: \a[micropython]
+
+= micropython/blink_gpio.py
+{file}
+{parent=MicroPython example}
+
+Toggle pin 0 twice per second. This could be used for example to blink LED on pin 0 once per second with this test circuit:
+
+``
+BOARD__1gp0____3gnd
+       |       |
+       R_2k    |
+       |       |
+       +-aLEDc-+
+``
+
+Tested on:
+
+* <RPI Pico W>
+
 = Microcontroller vs CPU
 {parent=Microcontroller}
 {wiki}
@@ -2470,7 +2498,7 @@ Serial from `cat /proc/cpuinfo`: 00000000c77ddb77
 = Raspberry Pi Pico
 {c}
 {parent=Raspberry Pi}
-{tag=Microcontroller}
+{tag=Microcontroller devboard}
 {title2=2021}
 
 Some key specs:
@@ -2501,9 +2529,10 @@ and uses picozero specific code. Rather, just use our examples from \a[rpi-pico-
 = Flash the Raspberry Pi Pico
 {parent=Raspberry Pi Pico getting started}
 
-This is a major design flaw, that the only easy default way is that you have to unplug, press bootsel, replug.
+This is a major design flaw, that the only easy default way is that you have to unplug, press bootsel, replug:
 * https://forums.raspberrypi.com/viewtopic.php?t=328795
 * https://www.reddit.com/r/raspberrypipico/comments/p9kmub/did_you_get_sick_of_unplugging_and_replugging/
+* https://raspberrypi.stackexchange.com/questions/149006/how-to-load-binary-into-raspberry-pi-pico-only-with-cli-without-gui
 
 = picotool
 {parent=Flash the Raspberry Pi Pico}
@@ -2605,6 +2634,10 @@ It is however possible to solder it yourself on <Raspberry Pi Pico W>.
 {parent=Raspberry Pi Pico variant}
 {title2=2022}
 
+= RPI Pico W
+{c}
+{synonym}
+
 Datasheet: https://datasheets.raspberrypi.com/picow/pico-w-datasheet.pdf
 
 Pinout: https://datasheets.raspberrypi.com/picow/PicoW-A4-Pinout.pdf
@@ -2707,14 +2740,15 @@ Examples at: <Raspberry Pi Pico W MicroPython example>.
 
 An upstream repo at: https://github.com/raspberrypi/pico-micropython-examples
 
-Our examples at: \a[rpi-pico-w/upython].
+Some generic Micropython examples most of which work on this board can be found at: <MicroPython example>{full}.
+
+Pico W specific examples are under: \a[rpi-pico-w/upython].
 
 The examples can be run as described at <Program Raspberry Pi Pico W with MicroPython>.
 
 * \a[rpi-pico-w/upython/led_on.py]: turn on-board LED on and leave it on forever. Useful to quickly check that you are still able to update the firmware.
 * \a[rpi-pico-w/upython/led_off.py]: turn on-board LED off and leave it off forever
 * \a[rpi-pico-w/upython/pwm.py]: <pulse width modulation>. Using the same circuit as the <rpi-pico-w/upython/blink_gpio.py>{file}, you will now see the external LED go from dark to bright continuously  and then back
-* \a[rpi-pico-w/upython/adc.py]: <analog-to-digital converter>. The program prints to the <UART> the value of the ADC on GPIO 26 once every 0.2 seconds. The onboard LED is blinked as a <heartbeat (computing)>. The hello world is with a <potentiometer>: extremes on GND and VCC pins of the Pi, and middle output on pin 26, then as you turn the knob, the uart value goes from about 0 to about 64k.
 
 = rpi-pico-w/upython/blink.py
 {file}
@@ -2731,15 +2765,7 @@ The <Micropython> code needs to be changed from the <Raspberry Pi Pico 1>, https
 {parent=Raspberry Pi Pico W MicroPython example}
 {tag=LED blinker}
 
-Toggle GPIO pin 0 on and off twice a second. Also toggle the on-board LED and print to UART for correlation. You can see this in action e.g. by linking an LED between pin 0 and one of the GND pins of the Pi, and the LED will blink. Circuit:
-
-``
-RPI_PICO_W__1gp0____3gnd
-            |       |
-            R_2k    |
-            |       |
-            +-aLEDc-+
-``
+Same as the more generic <micropython/blink_gpio.py>{file} but with the onboard LED added.
 
 = rpi-pico-w/upython/uart.py
 {file}
@@ -2760,6 +2786,30 @@ screen /dev/ttyUSB0 9600
 ``
 and a counter shows up there just fine!
 
+= rpi-pico-w/upython/adc.py
+{file}
+{parent=Raspberry Pi Pico W MicroPython example}
+{tag=LED blinker}
+
+\a[rpi-pico-w/upython/adc.py]: <analog-to-digital converter>.
+
+The program continuously prints to the USB the value of the ADC on GPIO 26 once every 0.2 seconds.
+
+The onboard LED is blinked as a <heartbeat (computing)>.
+
+The hello world is with a <potentiometer>: extremes on GND and VCC pins of the Pi, and middle output on pin GIO26, then as you turn the knob, the uart value goes from about 0 to about 64k.
+
+The 0 side is quite noisy and varies between 0 and 300 for some reason.
+
+In <Ciro's ASCII art circuit diagram notation>:
+``
+RPI_PICO_W__gnd__gpio26__5v
+            |    |       |
+            |    |       |
+            |    |       |
+         P__1____2_______3
+``
+
 = Program Raspberry Pi Pico W with C
 {parent=Program Raspberry Pi Pico W with X}
 {tag=MicroPython}

electronics.bigb

@@ -217,8 +217,15 @@ Asymmetric components have multiple letters indicating different ports. The capi
   ``
   DC_10---R_10---G
   ``
-  If the voltage is not given, it is assumed to be a <potentiometer>.
+  If the voltage is not given, it is assumed to be a variable voltage power supply.
 * `LED`: same as diode
+* `I`: <electric current> source. Ports:
+  * `s`: electron source
+  * `d`: electron destination
+* `P`: <potentiometer> source. Ports:
+  * `1`: one of the sides
+  * `2`: the middle
+  * `3`: the other side
 * `T`: <transistor>. The ports are `sgTd`:
   * `s`: source
   * `g`: gate
@@ -239,9 +246,6 @@ Asymmetric components have multiple letters indicating different ports. The capi
   --Tsgd--
      |
   ``
-* `I`: <electric current> source. Ports:
-  * `s`: electron source
-  * `d`: electron destination
 * `V`: <Voltmeter>. Ports:
   * `p`: positive
   * `n`: negative
@@ -670,6 +674,12 @@ It resists to change in <electric current>. Well seen at: <video LC circuit by E
 {parent=Resistor}
 {wiki}
 
+Variable <resistance> element.
+
+\Image[https://upload.wikimedia.org/wikipedia/commons/0/0a/Electronic-Component-Potentiometer.jpg]
+
+\Image[https://upload.wikimedia.org/wikipedia/commons/1/19/Potentiometer_symbol.svg]
+
 = Electrical resistance and conductance
 {parent=Resistor}
 {wiki}
@@ -680,6 +690,9 @@ It resists to change in <electric current>. Well seen at: <video LC circuit by E
 = Electrical resistance
 {parent=Electrical resistance and conductance}
 
+= Resistance
+{synonym}
+
 = Drude model
 {c}
 {parent=Electrical resistance}
@@ -1006,20 +1019,21 @@ Breadboards are a thing of beauty and wonder.
 {synonym}
 {title2}
 
+= <Microcontroller> devboard
+{parent=Microprocessor development board}
+
 = Arduino
 {c}
-{parent=Microprocessor development board}
+{parent=Microcontroller devboard}
 {wiki}
 
 = Micro Bit
 {c}
-{parent=Microprocessor development board}
+{parent=Microcontroller devboard}
 {title2=2016}
 {title2=BBC Micro Bit}
 {wiki}
 
-<Zephyr> support: https://docs.zephyrproject.org/2.7.0/boards/arm/bbc_microbit/doc/index.html
-
 <Bluetooth> support: not enough <RAM> for it, though in principle its chip/<transceiver> could support it! https://microbit-micropython.readthedocs.io/en/v1.0.1/ble.html
 
 Supported editors: https://microbit.org/code/
@@ -1096,9 +1110,41 @@ and the program starts executing immediately after flash ends.
 
 You can restart the program by clicking the reset button near the USB. When you push down the program dies, and it restarts as soon as you release the button.
 
-= Compile MicroPython code for Micro Bit locally
+= Program the Micro Bit with X
 {parent=Micro Bit}
 
+= Run <Zephyr> on Micro Bit
+{parent=Program the Micro Bit with X}
+{tag=Run Zephyr on X}
+
+Docs: https://docs.zephyrproject.org/2.7.0/boards/arm/bbc_microbit/doc/index.html
+
+Build worked:
+``
+west build -d build/microbit/hello_world -b bbc_microbit samples/hello_world
+``
+but flash failed:
+``
+west flash -d build/microbit/hello_world
+``
+Related: https://mattoppenheim.com/2018/06/24/using-udev-to-remove-the-need-for-sudo-with-the-bbc-microbit
+
+The build also generates a .hex file by default, and we've tried to flash it manually with:
+``
+cp build/microbit/hello_world/zephyr/zephyr.hex /media/ciro/MICROBIT/
+``
+but we failed to see it do anything with <zephyr/blink_gpio.c>{file}, so not sure if the flashing was broken or if the code was broken, or if we didn't find the IO pins correctly.
+
+= Run MicroPython on Micro Bit
+{parent=Program the Micro Bit with X}
+{tag=Run MicroPython on X}
+
+Bibliography:
+* https://tech.microbit.org/software/micropython/
+
+= Compile MicroPython code for Micro Bit locally
+{parent=Run MicroPython on Micro Bit}
+
 * https://stackoverflow.com/questions/73425359/is-it-possible-to-compile-microbit-python-code-locally
 * https://stackoverflow.com/questions/52691853/generating-micropython-python-code-hex-file-from-commandline
 
@@ -1114,11 +1160,9 @@ What that does is:
 * join it up with a prebuilt firmware that ships with uflash which contains the MicroPython interpreter
 * flashes that
 
-To build your own firmware see:
+To build your own firmware see: <Compile MicroPython code for Micro Bit locally on Ubuntu 22.04 with your own firmware>
 
-Got it working: <Compile MicroPython code for Micro Bit locally on Ubuntu 22.04 with your own firmware>
-
-= Compile MicroPython code for Micro Bit locally on Ubuntu 22.04 with your own firmware
+= Compile MicroPython code for Micro Bit locally on <Ubuntu 22.04> with your own firmware
 {parent=Compile MicroPython code for Micro Bit locally}
 
 TODO didn't manage from source <Ubuntu 22.04>, their setup bitrotted way too fast... it's shameful even. Until I gave up and went for the magic <Docker> of + https://github.com/bbcmicrobit/micropython[], and it bloody worked:
@@ -1219,7 +1263,7 @@ bibliography:
 
 = Program the Micro Bit in C
 {c}
-{parent=Micro Bit}
+{parent=Program the Micro Bit with X}
 {tag=C (language)}
 
 https://stackoverflow.com/questions/73877965/how-to-compile-c-c-code-into-a-hex-file-for-the-bbc-microbit

micropython/blink_gpio.py

@@ -1,5 +1,3 @@
-# Blink LED on pin 0. Tested on: RPI Pico W
-
 from machine import Pin
 from time import sleep
 

rpi-pico-w/upython/adc.py

@@ -1,10 +1,10 @@
 from machine import ADC, Pin
-import time
+from time import sleep
 
-led = machine.Pin('LED', machine.Pin.OUT)
+led = Pin('LED', Pin.OUT)
 adc = ADC(Pin(26))
 
 while True:
     print(adc.read_u16())
     led.toggle()
-    time.sleep(0.2)
+    sleep(0.2)

rpi-pico-w/upython/blink.py

@@ -1,7 +1,7 @@
-import machine
+from machine import Pin
 import time
 
-led = machine.Pin('LED', machine.Pin.OUT)
+led = Pin('LED', Pin.OUT)
 # For Rpi Pico (non-W) it was like this instead apparently.
 # led = Pin(25, Pin.OUT)
 

rpi-pico-w/upython/freenove_i2c_lcd_2004.py

@@ -0,0 +1,25 @@
+# https://github.com/Danielerikrust/LCD-20x4-Feed
+# https://github.com/Danielerikrust/LCD-20x4-Feed/blob/CH9121/LCD_Demo.py
+
+import time
+from machine import I2C, Pin
+from LCD_Display import LcdApi, I2CLcd
+
+"""LCD Section"""
+i2c = I2C(0, sda=Pin(20), scl=Pin(21), freq=400000) #GPIO 20 & 21 have no other function but I2C
+devices = i2c.scan()
+lcd = I2CLcd(i2c, devices[0], 4, 20) #For 4 row x 20 column LCDs
+#lcd = I2CLcd(i2c, devices[0], 2, 16) #For 2 row x 16 column LCDs
+print(lcd)
+# TODO: display turns on, recognizes I2C since lcd[0] variable not blow up, but nothing is showing up...
+lcd.topdata("THIS REMAINS STATIC")
+time.sleep(1)
+lcd.feed("^ These")
+time.sleep(1)
+lcd.feed("^^ Lines")
+time.sleep(1)
+lcd.feed("^^^ Feed")
+time.sleep(1)
+lcd.feed("^^^^ Up")
+time.sleep(1)
+lcd.feed("as you add new ones")