Ah; from the command line.
The mpremote app can be useful for that. The 'run' command allows MicroPython code held on the host computer to be run on the Pico. For example -Because the 'identify' program can be any MicroPython code it can determine a lot of things about the device it's running on, by calling MicroPython modules or peeking into internal on-chip information. This is using my own utility -The 'mpremote' app is extremely useful for other things as well so well worth installing as a MicroPython user. You should be able to install it with ' pip install mpremote'.
The mpremote app can be useful for that. The 'run' command allows MicroPython code held on the host computer to be run on the Pico. For example -
Code:
pi@Pi4B:/tmp $ cat identify.pyimport oslst = os.uname()for n in range(len(lst)): print(n, ":", lst[n])Code:
pi@Pi4B:/tmp $ mpremote connect /dev/ttyACM0 run identify.py0 : rp21 : rp22 : 1.25.0-preview3 : v1.25.0-preview.160.gc73204128.dirty on 2024-12-23 (GNU 12.2.1 MinSizeRel)4 : Raspberry Pi Pico with RP2040Code:
pi@Pi4B:/tmp $ mptool identifyIdentifying deviceDevice : Pico board with 2 MB Flash - Serial number E660583883278628Running : rp2 / micropythonVersion : v1.25.0-preview.160.gc73204128.dirty on 2024-12-23 (GNU 12.2.1 MinSizeRel)Created : Dec 23 2024 using Pico SDK 2.1.0USB Info : Not supportedPioAsm is : Stock 'rp2' PIO AssemblerDisk Size : 1,441,792 bytes, 1,408 KB, 1.4 MBDisk Used : 8,192 bytes, 8 KB 0.6%Disk Free : 1,433,600 bytes, 1,400 KB, 1.4 MB 99.4%Disk Addr : 0x100A0000 to 0x101FFFFFSafe Area : 0x1009F000 to 0x1009FFFF (4KB)Code Size : 655,360 bytes, 640 KB, 0.6 MBCode Used : 333,852 bytes, 326 KB, 0.3 MB 50.9%Code Free : 321,508 bytes, 313 KB, 0.3 MB 49.1%Mem Size : 246,144 bytes, 240 KB, 0.2 MBMem Used : 19,584 bytes, 19 KB 8.0%Mem Free : 226,560 bytes, 221 KB, 0.2 MB 92.0%Max 8-bit : Two 320 x 240 (HVGA) or 11 of 160 x 120 (QVGA)Max 4-bit : One 640 x 480 (VGA) or 5 of 320 x 240 (HVGA)Statistics: Posted by hippy — Mon Dec 23, 2024 11:24 pm
