This is a 128x64 monochrome display, 0.96" diagonal so very small.

This example initialises the display, and implements basic pixel, line drawing and text output.

This PR adds an example for the 200x200 monochrome e-ink display based on the SSD1681. Demonstrates use of the onboard SRAM and the SD card (possibly).

Checklist

• [x] documentation
• [ ] working example
• [x] Fritzing schematic and image
• [x] added to CMakeLists.txt
• [x] added to repo README

When I open the pico-example folder, the configuration process generate following error. How can I get sdk automatically download there?. It seems same for me when using command line instead of vsc, after type nmake

[main] Configuring folder: pico-examples 
[driver] Removing c:/Users/yuxiong/Documents/GitHub/pico-examples/build/CMakeCache.txt
[driver] Removing c:\Users\yuxiong\Documents\GitHub\pico-examples\build\CMakeFiles
[proc] Executing command: "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin\cmake.EXE" --no-warn-unused-cli -DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=TRUE -DCMAKE_BUILD_TYPE:STRING=Debug -Hc:/Users/yuxiong/Documents/GitHub/pico-examples -Bc:/Users/yuxiong/Documents/GitHub/pico-examples/build -G Ninja
[cmake] Not searching for unused variables given on the command line.
[cmake] Using PICO_SDK_PATH from environment (' ..\..\pico-sdk')
[cmake] CMake Error at pico_sdk_import.cmake:54 (message):
[cmake]   Directory 'C:/Users/yuxiong/Documents/GitHub/pico-examples/build/pico-sdk'
[cmake]   not found
[cmake] Call Stack (most recent call first):
[cmake]   CMakeLists.txt:4 (include)
[cmake] 
[cmake] 
[cmake] -- Configuring incomplete, errors occurred!

I'm not sure if it's related to the example code, but the serial output of the bmp280_i2c always shows incorrect values like :

Pressure = 36479.457 kPa
Temp. = -15.94 C

The good thing is that the values are not constant, if I put the sensor close to a heating source, the values quickly go up.

After some debugging, it seems that the calibration data I get from the BMP280 are wrong, here's a dump of the raw bytes I get from inside bmp280_get_calib_params() after i2c_read_blocking :

00 00 00 00 00 2F 94 00 4C 9D C0 7B F3 00 72 74 90 43 A3 2B BA 00 00 6B

According to the datasheet, it means dig_T1 and dig_T2 are zero but they state that compensation values are never zero...

I tried with 2 different BMP280 (3.3V) modules wired as in the example schematic but the result is the same.

I'm now out of idea :)

Does anyone have an idea on what could cause this issue?

Thanks in advance

I have updated a couple of files per @kilograham requests, but I have not tested any of these changes. They look sane. So from my point of view I think this branch can be merged.

As discussed with @lurch and referenced by @aallan this PR adds a PIO example to demonstrate sending and receiving infra-red codes in 'NEC' format: pio/ir_nec.

There are three sub-directories: the loopback example, and a library each for the transmit and receive functions. As requested I have included a README.adoc and wiring diagram along the lines of gpio/hello_7segment

I've left my name in the copyright message with the BSD-3Clause licence but I'm OK for you to change that if necessary. Incidentally I have followed the format of the other examples by adding the example_auto_set_url() stuff into CMakeLists.txt but I'm afraid I must admit I don't really know what I'm doing with that.

This PR reads and writes to the registers on the MCP9808 board. It sets the upper, lower and critical temperatures and reads the ambient temperature to 4dp by performing appropriate conversions. It checks to see that none of the limits have been surpassed and displays alerts if otherwise.

This PR adds a new example for the BMP280 temperature and pressure sensor via I2C. It takes care of reading sensor values and also the necessary conversion for the values to make sense. I'm not sure how much "cleaning up" is needed, for now all code is in one file for simplicity but a few definitions want to be in their own header file. Fritzing diagram and file included, accompanying documentation too.

Hi,

Just a heads up. I found that the pico examples weren't building and I needed to add:

set(PICO_SDK_PATH $ENV{PICO_SDK_PATH})

... to the start of the CMakeLists.txt file. Just before where it says "include(pico_sdk_import.cmake)".

Without this line, CMake was not using the PICO_SDK_PATH environment variable, as per section 8.2.3 of the Getting Started with Raspberry Pi Pico document.

Cheers.

Add a couple of examples that use the Max7219 via SPI.

Note, no Fritzing parts available for these particular panels, so diagrams omitted. Note that the wiring is very simple so this should not be an issue.

I've followed this guide step by step: https://www.element14.com/community/community/raspberry-pi/blog/2021/01/24/working-with-the-raspberry-pi-pico-with-windows

And everything works in "Developer Command Prompt for VS 2019" until the linking where I also have the "╗┐" in front of the directory path with the object files in.

This requires mbedtls to be added to the pico-sdk Connects to worldtimeapi.org and retrieves a web page Originally written by Floris Bos @maxnet

Fixes: #231

I get the hardfault when trying to run picow_freertos_ping_sys on pico-w, the picow_freertos_ping_nosys works fine.

Starting FreeRTOS SMP on both cores:
Version: 7.95.49 (2271bb6 CY) CRC: b7a28ef3 Date: Mon 2021-11-29 22:50:27 PST Ucode Ver: 1043.2162 FWID 01-c51d9400
cyw43 loaded ok, mac 28:cd:c1:03:e8:e0
API: 12.2
Data: RaspberryPi.PicoW
Compiler: 1.29.4
ClmImport: 1.47.1
Customization: v5 22/06/24
Creation: 2022-06-24 06:55:08
Connecting to WiFi...
connect status: joining
connect status: no ip
connect status: link up
Connected.
ping: send 142.251.35.196

Backtrace:

Starting program: /home/plebioda/pico/pico-examples/build/pico_w/freertos/ping/picow_freertos_ping_sys.elf
[New Thread 2]

Thread 1 received signal SIGTRAP, Trace/breakpoint trap.
isr_hardfault () at /home/plebioda/pico/pico-sdk/src/rp2_common/pico_standard_link/crt0.S:98
98      decl_isr_bkpt isr_hardfault
(gdb) bt
#0  isr_hardfault () at /home/plebioda/pico/pico-sdk/src/rp2_common/pico_standard_link/crt0.S:98
#1  <signal handler called>
#2  uxListRemove (pxItemToRemove=0x2000f4fc <ucHeap+9620>) at /home/plebioda/pico/FreeRTOS-Kernel/list.c:193
#3  0x10022800 in xTaskIncrementTick () at /home/plebioda/pico/FreeRTOS-Kernel/tasks.c:3635
#4  0x100200da in xPortSysTickHandler () at /home/plebioda/pico/FreeRTOS-Kernel/portable/ThirdParty/GCC/RP2040/port.c:507
#5  <signal handler called>
#6  0x10022e06 in prvMinimalIdleTask (pvParameters=0x0) at /home/plebioda/pico/FreeRTOS-Kernel/tasks.c:4332
#7  0x1001fd70 in pxPortInitialiseStack (pxTopOfStack=0x1001fec7 <prvDisableInterruptsAndPortStartSchedulerOnCore+18>, pxCode=0x20040fd8, pvParameters=0x10) at /home/plebioda/pico/FreeRTOS-Kernel/portable/ThirdParty/GCC/RP2040/port.c:187
#8  0x00000000 in ?? ()
(gdb) t 2  
[Switching to thread 2 (Thread 2)]
#0  0x10022f28 in prvCheckTasksWaitingTermination () at /home/plebioda/pico/FreeRTOS-Kernel/tasks.c:4690
4690    }
(gdb) bt
#0  0x10022f28 in prvCheckTasksWaitingTermination () at /home/plebioda/pico/FreeRTOS-Kernel/tasks.c:4690
#1  0x10022e28 in prvIdleTask (pvParameters=0x0) at /home/plebioda/pico/FreeRTOS-Kernel/tasks.c:4390
#2  0x1001fd70 in pxPortInitialiseStack (pxTopOfStack=0x1001ff21 <xPortStartScheduler+80>, pxCode=0x20041fc0, pvParameters=0xf) at /home/plebioda/pico/FreeRTOS-Kernel/portable/ThirdParty/GCC/RP2040/port.c:187
#3  0x100224ec in vTaskStartScheduler () at /home/plebioda/pico/FreeRTOS-Kernel/tasks.c:2888
#4  0x10000410 in vLaunch () at /home/plebioda/pico/pico-examples/pico_w/freertos/ping/picow_freertos_ping.c:63
#5  0x1000043e in main () at /home/plebioda/pico/pico-examples/pico_w/freertos/ping/picow_freertos_ping.c:80

In list.c:193 the pxItemToRemove->pxPrevious pointer is invalid:

(gdb) p *pxItemToRemove
$3 = {xItemValue = 31, pxNext = 0x2000f024 <ucHeap+8380>, pxPrevious = 0x1, pvOwner = 0x4, pvContainer = 0x1}

Using:

• pico-examples a7ad17156bf60842ee55c8f86cd39e9cd7427c1d
• pico-sdk: 2e6142b15b8a75c1227dd3edbe839193b2bf9041
• FreeRTOS: V202110.00-SMP-11-g8128208bd

It'd be very useful if there was a port of https://github.com/hathach/tinyusb/tree/master/examples/device/cdc_msc to the pico. I've tried my hands at it but never managed to get close. I don't have headers so I have no real way to debug

Greetings, I have a problem when I try to debug in VSCode with picoprobe. I copy the files from IDE/VSCode and I notice that I need to put "runToEntryPoint": "main" instead of "RunToMain". But the problem persist so I cannot find what I'm missing. It is possible that de documentation is obsolete in the part of "Chapter 7. Using Visual Studio Code" . My main OS is Arch but I tried with Ubuntu and I had the same problem.

This is the output when I try to debug.

Cortex-Debug: VSCode debugger extension version 1.6.7 git(b0f5563). Usage info: https://github.com/Marus/cortex-debug#usage Reading symbols from arm-none-eabi-objdump --syms -C -h -w /home/navarro/software/pico/my_project_picos/console_w/build/console.elf Reading symbols from arm-none-eabi-nm --defined-only -S -l -C -p /home/navarro/software/pico/my_project_picos/console_w/build/console.elf Launching GDB: arm-none-eabi-gdb -q --interpreter=mi2 1-gdb-version Launching gdb-server: /home/navarro/software/pico/openocd/src/openocd -c "gdb_port 50000" -c "tcl_port 50001" -c "telnet_port 50002" -s /home/navarro/software/pico/openocd/tcl -f /home/navarro/.vscode/extensions/marus25.cortex-debug-1.6.7/support/openocd-helpers.tcl -f interface/picoprobe.cfg -f target/rp2040.cfg Please check TERMINAL tab (gdb-server) for output from /home/navarro/software/pico/openocd/src/openocd Finished reading symbols from objdump: Time: 24 ms Finished reading symbols from nm: Time: 33 ms OpenOCD: GDB Server Quit Unexpectedly. See gdb-server output in TERMINAL tab for more details.

This is my settings.json

{ // These settings tweaks to the cmake plugin will ensure // that you debug using cortex-debug instead of trying to launch // a Pico binary on the host "cmake.statusbar.advanced": { "debug": { "visibility": "hidden" }, "launch": { "visibility": "hidden" }, "build": { "visibility": "default" }, "buildTarget": { "visibility": "hidden" } }, "cmake.buildBeforeRun": true, "C_Cpp.default.configurationProvider": "ms-vscode.cmake-tools", "cortex-debug.openocdPath": "/home/navarro/software/pico/openocd/src/openocd", "cortex-debug.gdbPath": "arm-none-eabi-gdb",

}

and this is my lunch.json

{ "version": "0.2.0", "configurations": [ { "name": "Pico Debug", "cwd": "${workspaceRoot}", "executable": "${command:cmake.launchTargetPath}", "request": "launch", "type": "cortex-debug", "servertype": "openocd", // This may need to be arm-none-eabi-gdb depending on your system "gdbPath" : "arm-none-eabi-gdb", "device": "RP2040", "configFiles": [ "interface/picoprobe.cfg", "target/rp2040.cfg" ], "svdFile": "${env:PICO_SDK_PATH}/src/rp2040/hardware_regs/rp2040.svd", "runToEntryPoint": "main", // Work around for stopping at main on restart "postRestartCommands": [ "break main", "continue" ], "searchDir": ["/home/navarro/software/pico/openocd/tcl"], "showDevDebugOutput": "parsed" } ] }

Since I wanted to learn FreeRTOS and lwIP in combination on the RP2040, I compiled the "Pico-W FreeRTOS iperf server" example.

The access point I used is another Pico-W running the "Pico-W Access Point" example without any modifications.

I also connect my Linux laptop to the same access point and all devices get their IPv4 addresses via DHCP server integrated with the access point example. No other devices except the Pico-W and the laptop are connect to the access point.

When I run the iperf server in "NO_SYS" mode, everything is fine, iperf reports around 12MBit/s. I can happily repeat the test, ping the device in parallel and even run nmap against it. The LED just keeps on blinking.

With the "sys" example however, the LED starts blinking as soon the board has connected to it's AP and is ready to run the tests. However, when I start the iperf client on my laptop, the LED will stop blinking eventually. The Pico-W running the iperf sys example is still pingable and futher iperf runs are possible. However, the LED will just stay off.

I haven't yet digged deep into it. It might be a bug in FreeRTOS or its rp2040 "port" that makes it stop scheduling tasks properly, it could be a bug in the cyw driver or firmware that either stops driving the LED or the SPI channel is blocked by the WiFi traffic and as such the SPI traffic regarding the LED gets lost. It could also be lwIP or the cyw driver corrupting some parts of memory and as such the LED blinking tasks is no longer functioning ...

Again, no issues with the NO_SYS variant of the freertos iperf server example.