And a well deserved one! Sorry, I know this was pretty basic compared to compiling your own kernel to #define out the sections of the board you sawed off with a roto-tool, but I'm new to the Pi ;-) If you can think of a way to combine an ESP32 and a Pi, it might be fun to do a collab at some point... Right now, my biggest use of the Pi is as the master controller for a bunch of ESP32 Christmas lights: studio.ruclips.net/user/videoHk7ByiVPACc/edit
@@DavesGarage There are a few projects I have in mind... I've only used the 8266, never the ESP32 (yet), and I have my eye on a couple of the Pico boards with built-in WiFi too. So far though I'm completely backlogged with some really fun Pi CM4 builds enough that I don't get the time for microcontroller fun :( Hopefully that changes next year!
@@DavesGarage Isn't red shirt jeff the one who sawed that poor raspberry pi? No but all jokes aside I was recently playing with github copilot and it's amazing. I made it write a simple code for my esp to read data from various sensors and make a post request containing some data. And a python server built on flask to save this data on a database running in a docker container. I also managed to run my python server on my android phone using termux and save the files on a .db file on the phone and it was so much fun to build.
Hello Dave! Post more tips and tricks on debugging, that is significant amount of effort when coding and looking for non obvious problems. I like this video very much! Also, you made huge progress and now you are natural friendly youtube fraggles. Its pleasure to watch you!
One of the most useful tips when working with a pi: In Raspberry Pi Imager press CTRL+SHIFT+X to bring up the advanced options. Lets you setup SSH, Wi-Fi, mDNS name, and you can save these settings so every pi from now on has these settings by default when flashed with Raspberry Pi Imager.
Dave I can't believe you just made this video. I bought a Freenove Ultimate Starter Kit for my Pi 3B+, and just the other day I completed the very first project, the one where you flash the LED on and off. For years I've wanted to learn more about how electronics works (outside of school), and this finally gives me the chance. Tip: Make sure your jumper wires are connected tight into the breadboard. The one I had leading back to ground was loose, so I had to wiggle it. Then it started working. :-D
I used wiringPi way back in 2014 for some undergrad projects in my ECE program. Nice to see a much more refined workflow using Visual Studio and ssh to do things wirelessly!
Hi Dave, amazing video! Really good to see you more relaxed on the camera. Just finished you book by the way, it was really informative and answered many questions !
The first thing I noticed when I started working up a new project for a pi was that my VS community installation, which I may have pushed all the buttons on during installation, has a c++ raspberry pi project already in place ["Raspberry Pi Project", "A blinking LED app using WiringPi for Raspberry Pi."]. This sets things up quite nicely, including sorting out wiringPi. The little getting started bit also gives some nice instructions for setting up the remote.
Great video! I've recently started doing remote debugging of STM32 with ST-Link, and there's truly no better way to dig deep into those tricky bugs than direct debugging. Before getting the ST-Link I was just printing things out to the serial console, just about the slowest and most tedious way to track down issues.
Did you buy a hardware debugger or did you manage it with software. I spent few days during a project deadline and just didn't have time to finish it. Any tips are appreciated
ST-Link or any other debugger for that matter are awesome. I use them to get memory snapshots while testing. Really useful when a problem could be caused by either software, hardware, electronics or mechanical.
Absolutely interested in a similar setup for the ESP32! We have a work project that uses one of those, and we just use the vanilla ESP-IDF with VS Code to edit and printf debugging :)
Bought your book - I think it's more stories so I should like. Also consider adding a short monetized amazon list for things you play with, etc. Besides sending .001 cents your way occasionally it also helps us by playing with discussed content vs debugging the different setup activities.
few notes - microsoft code can also be installed on the pi, if you want to code locally on the pi. sql server can be installed on linux... haven't tried on the pi, but i've got it on a x86 version running on a NUC. Rasp pi just released a new version 2 w ... would like to see what you can do with that 64bit monster... .as they got 4 cores on a pi zero... anyways... keep up the good work! Thanks, Mike.
For everyone that is getting Severity Code Description Project File Line Suppression State Error -E or -x required when input is from standard input There is a stray " - " somewhere in your settings. For me it was at linker --> all options --> Additional options " - %(AdditionalOptions)" it should be "%(AdditionalOptions)"
I really could have used this a few years ago. I managed get similar results on an Eclipse based IDE and remote debugging. Or did i cross compile? I cant say i remember anymore. As much as i'm not a huge fan of Visual Studio, it is a lot better IDE than Eclipse. It was not for a PI, but for a custom Computer On a Module that run Linux. Very similar to the current Raspberry PI CM 4 modules. I will certainly use this video as a reference next time i need to get a similar project up and running. Thank you Dave. PS: The book started off great and i will read the rest of it while on vacation in the next couple of days. Cant wait for that.
Dave puts the curly braces on separate lines which I believe is the proper way. I read a number of books on programming styles and it is important that your code is readable because sooner or later somebody else is going to inherit your code and try to understand it. Fortunately, Visual Studio has a curly brace setting for both types of programmers.
7:59 The pi 3 is 64 bit capable. But the older ones are not. This list includes original pi, B+, Pi2, 1st gen zero's and other pi's that are based on them.
Did you specifically install a 64-bit version of Raspbian? Even though Pi3 and Pi4 have 64-bit processors, the default Raspbian image is 32-bit, for compatibility purposes (and 64-bit build is available as beta).
Hey, Dave, I'm curious to know what you heard during the 90s and early 00s about Linux inside Microsoft, if and when you heard something about Microsoft treating it like a competitor, or if it just ignored completely, if the employees experimented with Linux, if they took inspiration in some things from Linux distros, anyway, anything in that sense. Thanks and congrats for your channel!
Nice, Great but I have one question: can you please give me how to type a path to the wiringPi library? Under vc++directories..it is not so clear on this video
Great! How to use remote includes, libraries, such as SDL, zmq? I have some headers in /usr/lib /usr/local/lib /usr/include/SDL /usr/local/include, how i can use them?
Went by the adding the include directories too fast - this was the part that killed me when trying to use the blinky project direct. Where are those $(xxxx) defined?
Great video! I have some question. at 9:01, how can i access the WiringPi libraries installed(by me) inside WSL debian? are you using WSL1 or WSL2? How do you create the $(LinuxIncludePath) macro inside visual studio to point to WSL's linux virtualmachine file system? My current idea is to pre-build & install libraries for raspberry pi inside the WSL debian system. Afterwards, when i build & debug in visual studio 2022, i include and link to WSL debian's linux include path. And it will do a remote-build on a raspbery pi , and i can debug from it as well. Is this approach the way?
I think this a great and informative video --Thanks. I have tried for many hours to get this to work on Visual Studio 2022 with Nov-Dec update. It has a R P template for blink. I cannot get it to build. Would you consider a new video on this subject showing how to do this on Visual Studio 2022. I thought it would be easy but I cannot do it. Thanks
There is still very much reason to keep printf debugging. Main reason? Timing. Set a breakpoint, and the time for that thread stops. But not the time for the rest of the world. This can matter a lot in an embedded device, a device driver or some fancy network server. But there is one more thing to consider with debuggers - it's too easy to turn off the brain and enter single-step mode instead of thinking about symptoms and look at code. Quite a lot of bugs can be caught with just brain power, since it's often not that many source code lines that can cause the error. It's way more satisfying to hear about a bug and 10 minutes later point at the buggy code line without having used debugger or printf().
printf, particularly over serial, also disrupts timing. You can't do it under interrupt either, on some. Better to have multiple tools in your toolbox, I figure!
@@DavesGarage Depends. printf()/sprintf() + interrupt-driven round-robin UART send buffer can be used quite well on some platforms even from ISR. Single-char print with round-robin send buffer can always be used since a round-robin buffer does not need critical sections as long as there is only one producer. But it slows the ISR time with total time to process the formatting string (or putc) and insert into send buffer. And the UART transmit ISR may consume a few % CPU. Obviously, an ISR should settle for easy prints if it's often activated - a single byte telling which branch it selected (rx, tx, parity, overflow, "oops" ...) means 115 kbaud debug UAER can trace 10k interrupts/second. A single byte from an ISR can also be detected even if it breaks into a normal printout from outside ISR by selecting good characters. Also - some processors have a virtual serial port where the printouts can use JTAG interface to print to output window of IDE. Obviously there is sometimes the one-step-up option - real-time capture of the running program with recording, but that tends to require more $ than hobbyists prefer and not all chips can stream this data to a JTAG with buffer RAM.. But it is so nice if the program sometimes suffers an exception - to be able to step back in time some thousand instructions in the debugger and see the state of the program step-by-step while it walked into the death trap. But putc/print means an embedded device (or a multithreaded application) can continue to process CAN data, feed a SPI link, respond to network requesrs etc while still giving the relevant trace info. Moving to an RPi, the raw print capacity is many MB/s while still handling real-time communications.
@@DavesGarage And yes - definitely better to have multiple tools. There are no bigger fools than people with a hammer that does their best to just look for nails...
Nah. It's a cheap crap computer. About as powerful as 20 years old dual-cpu PentiumIII server with extra hardware support for encoding and decoding h264 FullHD video up to certain bitrate :) Or about half as powerful as your phone. You can do whatever you want with it - web server, print server, media player, you may stream audio from usb sound card or video (well, this on the edge) and you may connect keyboard and monitor and use it as a PC - likely not much powerful, i never tried it.
@@DavesGarage i was too young for commodore but i used this in qbasic. i would memcopy a background memory block to sprite memory block then draw bitmaps using poke on to that layer then memcopy directly to video buffer using asm. this was able to handle a crapload of sprites on a slow system without much trouble. i even wrote a simple 3d engine which ran pretty well considering it was running on qbasic 4.5
Definitely a vid on remote ESP32 w/ vscode!
Is that even possible?
please! That would be incredible!
+1 @Dave
Definitely interested
Please :)
1:40 I had an excellent sleep last night, thanks!
I thought I might find you in the comments.
And a well deserved one! Sorry, I know this was pretty basic compared to compiling your own kernel to #define out the sections of the board you sawed off with a roto-tool, but I'm new to the Pi ;-)
If you can think of a way to combine an ESP32 and a Pi, it might be fun to do a collab at some point... Right now, my biggest use of the Pi is as the master controller for a bunch of ESP32 Christmas lights: studio.ruclips.net/user/videoHk7ByiVPACc/edit
@@DavesGarage There are a few projects I have in mind... I've only used the 8266, never the ESP32 (yet), and I have my eye on a couple of the Pico boards with built-in WiFi too. So far though I'm completely backlogged with some really fun Pi CM4 builds enough that I don't get the time for microcontroller fun :(
Hopefully that changes next year!
@@DavesGarage Isn't red shirt jeff the one who sawed that poor raspberry pi? No but all jokes aside I was recently playing with github copilot and it's amazing. I made it write a simple code for my esp to read data from various sensors and make a post request containing some data. And a python server built on flask to save this data on a database running in a docker container. I also managed to run my python server on my android phone using termux and save the files on a .db file on the phone and it was so much fun to build.
@@makkam7575 that sounds great, maybe one you will do a video for us all, thanks
Joke's on you Dave, most bosses haven't coded in decades ;)
Good point! But keep in mind I was a boss too, so there are many kinds 🙂
I once had a boss who enjoyed cracking software.
And we're still cleaning up the mess they made.
@@DavesGarage jokes on you most boss dont code. lol
@@masternobody1896 - I've had several bosses that coded.
You're an excellent teacher. You repeat things that are really important, but you don't repeat them too much.
Hello Dave! Post more tips and tricks on debugging, that is significant amount of effort when coding and looking for non obvious problems.
I like this video very much!
Also, you made huge progress and now you are natural friendly youtube fraggles. Its pleasure to watch you!
One of the most useful tips when working with a pi: In Raspberry Pi Imager press CTRL+SHIFT+X to bring up the advanced options. Lets you setup SSH, Wi-Fi, mDNS name, and you can save these settings so every pi from now on has these settings by default when flashed with Raspberry Pi Imager.
I would absolutely love a video about debugging an ESP32 in the same way.
Wasn't expecting to be transported back to my childhood. Thanks for reminding me of the Friendly Giant.
Dave I can't believe you just made this video. I bought a Freenove Ultimate Starter Kit for my Pi 3B+, and just the other day I completed the very first project, the one where you flash the LED on and off. For years I've wanted to learn more about how electronics works (outside of school), and this finally gives me the chance. Tip: Make sure your jumper wires are connected tight into the breadboard. The one I had leading back to ground was loose, so I had to wiggle it. Then it started working. :-D
Wow, a Friendly Giant reference at the end. Someone’s showing their Canuckishness.
PS Hello from Jasper avenue in “Siberia”
Awesome! Stop by that little mall you have in town and treat yourself to something ;-)
I used wiringPi way back in 2014 for some undergrad projects in my ECE program. Nice to see a much more refined workflow using Visual Studio and ssh to do things wirelessly!
Hi Dave, amazing video! Really good to see you more relaxed on the camera. Just finished you book by the way, it was really informative and answered many questions !
Thanks, Dave. Haven't used VS for work in almost 15 years as I'm in a 100% Linux shop. I'll add this to the list of things I want to play with bin 😁
The first thing I noticed when I started working up a new project for a pi was that my VS community installation, which I may have pushed all the buttons on during installation, has a c++ raspberry pi project already in place ["Raspberry Pi Project", "A blinking LED app using WiringPi for Raspberry Pi."]. This sets things up quite nicely, including sorting out wiringPi. The little getting started bit also gives some nice instructions for setting up the remote.
I recall using pigpio for all my pi gpio access needs. It was a pretty good library
I knew this was possible, but never had the patience to figure out how to configure it
Great video! I've recently started doing remote debugging of STM32 with ST-Link, and there's truly no better way to dig deep into those tricky bugs than direct debugging. Before getting the ST-Link I was just printing things out to the serial console, just about the slowest and most tedious way to track down issues.
Did you buy a hardware debugger or did you manage it with software. I spent few days during a project deadline and just didn't have time to finish it. Any tips are appreciated
Printf doesn't help a stack out of memory causing a kernel panic reboot.
ST-Link or any other debugger for that matter are awesome. I use them to get memory snapshots while testing. Really useful when a problem could be caused by either software, hardware, electronics or mechanical.
I do this kind of debugging daily. I do this on game consoles. Attaching and launching on another pc. It's great!
Debbuger... what's a debugger?
I just use c out for variables and c in for pauses
🙃
poor man debugger
Yes to debugging an ESP32. Man this is going to make my work on a Pi much better.
Thank you, Dave. Still working with the LED's, myself. This was a good C++ breakdown for me. Awesome!
Absolutely interested in a similar setup for the ESP32! We have a work project that uses one of those, and we just use the vanilla ESP-IDF with VS Code to edit and printf debugging :)
I can magically do this over ssh with lldb. :-D I would DEFINITELY like to see this on an ESP32.
I enjoyed that Bill OReilly reference. 🤣
Love Studio's dark background and character-cell font you set up there.
I love the font in your terminal!
Bought your book - I think it's more stories so I should like. Also consider adding a short monetized amazon list for things you play with, etc. Besides sending .001 cents your way occasionally it also helps us by playing with discussed content vs debugging the different setup activities.
You sir. Just changed my life. Wow.
"Let's try it live ... that's always advisable."
lmao
Definitely a video on Esp32 debugging via Visual studio. And greetings to Jeff Geerling!
few notes - microsoft code can also be installed on the pi, if you want to code locally on the pi. sql server can be installed on linux... haven't tried on the pi, but i've got it on a x86 version running on a NUC. Rasp pi just released a new version 2 w ... would like to see what you can do with that 64bit monster... .as they got 4 cores on a pi zero... anyways... keep up the good work! Thanks, Mike.
Esp32 remote debug video would be handy
For everyone that is getting Severity Code Description Project File Line Suppression State
Error -E or -x required when input is from standard input
There is a stray " - " somewhere in your settings.
For me it was at linker --> all options --> Additional options " - %(AdditionalOptions)" it should be "%(AdditionalOptions)"
Great video! Yes on a video to debug esp32 on VS Code! Love this channel!
Thanks for this video Dave. I'm developing on the pi A+ and it's as slow as a wet week but VS is way better than nano and native gdb.
Thanks so much! I tried to get Wiringpi working last year, but had trouble. Looking forward to getting back into it
I really could have used this a few years ago. I managed get similar results on an Eclipse based IDE and remote debugging. Or did i cross compile? I cant say i remember anymore. As much as i'm not a huge fan of Visual Studio, it is a lot better IDE than Eclipse.
It was not for a PI, but for a custom Computer On a Module that run Linux. Very similar to the current Raspberry PI CM 4 modules.
I will certainly use this video as a reference next time i need to get a similar project up and running. Thank you Dave.
PS: The book started off great and i will read the rest of it while on vacation in the next couple of days. Cant wait for that.
Another great Vid, would also like to see ESP32 version
Great video. Yes please on the ESP32 debug like a BOSS.
You are a hero and totally my favorite youtuber.
Hi Dave, yes Please, it would be very nice with a video on setting up and debugging ESP32 on VSC (-:
Thanks for the tutorial, this opens up a new simpler possibility for me
Dave puts the curly braces on separate lines which I believe is the proper way. I read a number of books on programming styles and it is important that your code is readable because sooner or later somebody else is going to inherit your code and try to understand it. Fortunately, Visual Studio has a curly brace setting for both types of programmers.
This is a gamechanger for me. Brilliant!
In B4 he automates his truck and makes it self driving and first drives his truck with a laptop in debugger mode.
Great video, always nice learning new things. Had a pi when I was younger, would be cool to buy one and play around with it
I used this while working on a Linux target at a past job. Eclipse was horrendous for the big project we were working on.
“Let’s do it live like Bill O’Reilly”. 😂😂😂😂😂 hehe
I knew visual studio was this powerfull, i learned programming with Visual Studio btw
ESP32 like a boss debugging - YES PLEASE !
Great video and reviews
I used to really enjoy debugging through GDB. After debugging daily via visual studio for years now, I think I'd hate using GDB.
7:59 The pi 3 is 64 bit capable. But the older ones are not.
This list includes original pi, B+, Pi2, 1st gen zero's and other pi's that are based on them.
Thanks!
Did you specifically install a 64-bit version of Raspbian? Even though Pi3 and Pi4 have 64-bit processors, the default Raspbian image is 32-bit, for compatibility purposes (and 64-bit build is available as beta).
Wish i knew this before, when i coded a LED spinning globe to display some bitmaps. Would had saved me a lot of time. :)
Debugging like a boss: "Debug this by tomorrow or you will get fired."
Just what I need for my school project
Hey, Dave, I'm curious to know what you heard during the 90s and early 00s about Linux inside Microsoft, if and when you heard something about Microsoft treating it like a competitor, or if it just ignored completely, if the employees experimented with Linux, if they took inspiration in some things from Linux distros, anyway, anything in that sense. Thanks and congrats for your channel!
Thanks for still doing videos
More to come!
Very nice. Showing it for a PiCo would also be useful.
Would love the esp32 vid!
Nice, Great but I have one question: can you please give me how to type a path to the wiringPi library? Under vc++directories..it is not so clear on this video
Neat. Visual Studio is almost as featureful as emacs now! :P
In-fact, more ESP32 stuff would be epic. I loved this video tho!
Great! How to use remote includes, libraries, such as SDL, zmq? I have some headers in /usr/lib /usr/local/lib /usr/include/SDL /usr/local/include, how i can use them?
Yes, Please!!! Debugging on the ESP32 using VS-Code. Thanks
Went by the adding the include directories too fast - this was the part that killed me when trying to use the blinky project direct. Where are those $(xxxx) defined?
But how to build WiringPi on Windows to work with that includes and lib file? it's kind a blind spot totally not covered in video. Sad (
Me too with remote ESP32 w/ vscode. Thanks!
yes please show me how to debug the ESP32 like a BOSS with visual studio. i am very interested
Who would win?
❌ Fully-featured integrated debugger, allowing remote cross-platform debugging
✔️ One printy boi
Please let us know how you normally set up your build dependencis in Visual Studio, since I'm sure I'm missing a lot of great tricks there too.
i would love the vsc one cause i dont have access to visual studio due to linux.
thanks for this one Dave , very helpful ! =)
Great video! I have some question. at 9:01, how can i access the WiringPi libraries installed(by me) inside WSL debian? are you using WSL1 or WSL2? How do you create the $(LinuxIncludePath) macro inside visual studio to point to WSL's linux virtualmachine file system?
My current idea is to pre-build & install libraries for raspberry pi inside the WSL debian system. Afterwards, when i build & debug in visual studio 2022, i include and link to WSL debian's linux include path. And it will do a remote-build on a raspbery pi , and i can debug from it as well. Is this approach the way?
love your rolex submariner
Wow, thanks, that has my limit of Linux in it, but well worth it.
Now can you get bare metal c++ working in VS please :)
Hi Dave just been watching this again. Is this possible with VS Code ? Studio code is a bit rich for my budget.
Please do a ESP32 setup tutorial, that would be awesome 🙂
I think this a great and informative video --Thanks. I have tried for many hours to get this to work on Visual Studio 2022 with Nov-Dec update. It has a R P template for blink. I cannot get it to build. Would you consider a new video on this subject showing how to do this on Visual Studio 2022. I thought it would be easy but I cannot do it.
Thanks
"Let's try it live. That's always advisable."
😂🤣
Excellent content, thanks for sharing.
Does VSCode do: 1. Python 2. Python Debugging & 3. Remote Python Debuggin on a Pi??
Yes to 1 & 2, don’t know on 3, but I’ve been putting it off all week, I’ll let you know.
Hi Dave. Cool video! Do you know if I can do such a thing with a c# console application and a raspberry pi 4?
Text in those critical properties windows is WAY too small. Here is where you need to spend time as this is where Visual Studio is difficult!!!!
I must admit when I saw the title I thought you'll be talking about Segger's J-link.
Nice video nevertheless.
ESP32 debugging for everyone!
There is still very much reason to keep printf debugging. Main reason? Timing. Set a breakpoint, and the time for that thread stops. But not the time for the rest of the world. This can matter a lot in an embedded device, a device driver or some fancy network server.
But there is one more thing to consider with debuggers - it's too easy to turn off the brain and enter single-step mode instead of thinking about symptoms and look at code. Quite a lot of bugs can be caught with just brain power, since it's often not that many source code lines that can cause the error. It's way more satisfying to hear about a bug and 10 minutes later point at the buggy code line without having used debugger or printf().
printf, particularly over serial, also disrupts timing. You can't do it under interrupt either, on some. Better to have multiple tools in your toolbox, I figure!
@@DavesGarage Depends. printf()/sprintf() + interrupt-driven round-robin UART send buffer can be used quite well on some platforms even from ISR. Single-char print with round-robin send buffer can always be used since a round-robin buffer does not need critical sections as long as there is only one producer.
But it slows the ISR time with total time to process the formatting string (or putc) and insert into send buffer. And the UART transmit ISR may consume a few % CPU.
Obviously, an ISR should settle for easy prints if it's often activated - a single byte telling which branch it selected (rx, tx, parity, overflow, "oops" ...) means 115 kbaud debug UAER can trace 10k interrupts/second. A single byte from an ISR can also be detected even if it breaks into a normal printout from outside ISR by selecting good characters.
Also - some processors have a virtual serial port where the printouts can use JTAG interface to print to output window of IDE. Obviously there is sometimes the one-step-up option - real-time capture of the running program with recording, but that tends to require more $ than hobbyists prefer and not all chips can stream this data to a JTAG with buffer RAM.. But it is so nice if the program sometimes suffers an exception - to be able to step back in time some thousand instructions in the debugger and see the state of the program step-by-step while it walked into the death trap.
But putc/print means an embedded device (or a multithreaded application) can continue to process CAN data, feed a SPI link, respond to network requesrs etc while still giving the relevant trace info. Moving to an RPi, the raw print capacity is many MB/s while still handling real-time communications.
@@DavesGarage And yes - definitely better to have multiple tools. There are no bigger fools than people with a hammer that does their best to just look for nails...
Have you done something similar with VS Code? with python code
yes please for the esp32 video
Hey Dave, what processor you flexing there? Also, I'm going for a Timmy run. Want something?
I thought the Pi was made for students to learn how to code on.... so it didn't occur to me to question why you would do an episode on it.
Nah. It's a cheap crap computer. About as powerful as 20 years old dual-cpu PentiumIII server with extra hardware support for encoding and decoding h264 FullHD video up to certain bitrate :) Or about half as powerful as your phone. You can do whatever you want with it - web server, print server, media player, you may stream audio from usb sound card or video (well, this on the edge) and you may connect keyboard and monitor and use it as a PC - likely not much powerful, i never tried it.
Does the visual studio code have a similar extension?
Friendly Dave
Just out of curiosity, Dave, do you *really* type that fast? Ever had it measured?
8:40 is sped up if you look on the camera. Was there a specific part you were thinking of?
I play it at double speed to find out how fast he _really_ types. ;-)
Nice video. Do you have any info on the flame spiral looking thing in the top-right? Looks cool.
Yup, search for tiki lamp on the channel!
Yes, Dave! Yes I really would like to debug an ESP32 remotely!
Is it also possible for its little brother, the ESP8266?
I do code for the PI in python
remembering the good old days of peek and poke
POKE 53281, 0
POKE 53280, 0
POKE $0286, 0
SYS $E544
; ARGH! I'M BLIND! Sorry I only know it in hex ;-)
@@DavesGarage i was too young for commodore but i used this in qbasic. i would memcopy a background memory block to sprite memory block then draw bitmaps using poke on to that layer then memcopy directly to video buffer using asm. this was able to handle a crapload of sprites on a slow system without much trouble. i even wrote a simple 3d engine which ran pretty well considering it was running on qbasic 4.5
Thanks Dave
ESP32 debugging video would be nice please. Also have you played with the Pi pico yet?