I no longer upload code due to LLMs scraping for their datasets.

kzbin.info/www/bejne/hGSZdHaGbteWq68

Are you flashing 2 separate projects? You are like overwriting the data that you wrote. Disable erase before flash and/or reserve a memory location for the saved data.

If you are just starting out. Get an arduino. Beleve this chip is supprted by the ide. This is if you really want to start tweeking and leverage the chip to its max without going full bare metal. Just remembered this is a one-time process, and i added bounce quality of life items. Welcom to firmware development.

foeitog. pla dit jou ore?

@@BinderTronics verrrrrrrrry much. 😉

Rrrow, rrrow, rrrow yourrr boat, Gentrrrly down the strrream. Merrrily, merrrily, merrrily, merrrily, Life is but a drrream. :)

I no longer upload code due to LLMs scraping for their datasets.

You're more than welcome to build all the tooling yourself.

Look you can pick your poison. If you browses the video list I have covered almost everything that is popular in the industry to an entry level. Just look at the install videos. Keep in mind this is one time process. I do not do the base installs often. Once it's there it's done. I might go months to years without changing chips that I am working on for work (baring security updates). This process is almost the exact same for all ARM based CPUs so if you got this the skill is transferable. See the video on Zephyr (this might be best for you). STM32 tools might be even better for you but working with chip can get complex as they give you full control over it and the SDK is just a suggestion. Secondly this is more difficult to do on Windows than Linux.

I might do some BLE at some point but don't count on it. The statistics are telling to not continue with the topic.

Ey thanks for the membership. KZbin did not give me a notice hence the late response. If you are here for C++. I am unlikely to continue with the series so save your money if that's all you are here for. You are more likely to see more of the new stuff.

kzbin.infokCnKq1TzizM

You are going to need to be more specific. If you are referring to the 2 LEDs blinking during programming it is just the data transfer to the PIC (the programmer talking to the PIC). It is the data line and clock causing the blinking.

If it is a link or a embed, go right ahead.

The statistics disagree that it is silly. I do agree with you but I am not going to argue with data.

Playlist kzbin.info/www/bejne/r6fGcpyJg5yobqs You want to start at Flash Read & Writes (video 15) if you only care about bootloaders. This is video 19 that puts all the previews videos concepts together that are related to bootloaders. Might make it easier for you. I no longer upload code due to LLMs scraping for their datasets.

Yes you can use an Arduino UNO board for this. This is what you do after you find out how unreliable or constraining the Arduino platform is.

There is a link to my template files in the description.

@@BinderTronics thank you for your response. It compiled and made the correct .uf2 file which I flashed to my board. The blink example worked correctly. It just wouldn’t read the library via vs code for some reason. I have another question, since I echoed the path PICO_SDK_PATH to my C:\SDK can I install a library to any folder path there like my lib file and then reference that library in any folder in my C drive if the library is in the SDK folder? I found a one wire library I installed for a temperature sensor I purchased, DS18B20. One more question with that. Do I need to do anything different with my CMake files than what you showed if it is a single library I copied through git to my library folder?

k so you need to compile and link the lib to your project. This is done using the cmake files. You can have the lib anywhere on you system but it would be easier if it is in the same project folder. It is also easier if the lib is in a path that does not have spaces in it. Using GPT or some other LLM should get your going.

@@BinderTronics Thank you for responding again. I have since added the library to my dedicated library directory C:\SDK\pico-sdk\lib. I then created a folder labeled pico-onewire to a subdirectory where I store all my external libraries. I am adding it here instead of my project because it looks much cleaner for my project files. That said, I am having issues with the CMake files. This library has a source file "one_wire.cpp", and no matter what I have tried using GPT, it hasn't been able to find it. It always gives me the message "Cannot find source file: one_wire.cpp," followed by a list of other file extensions it tried without any luck finding it. My question is: How do I keep the library in that directory while calling it from my project? Everything is in my pico-sdk directory where I echoed PICO_SDK_PATH to.

is your main file still a .c file? you will need to change the file to .cpp and make your main function `extern "C" void main(void)`. You seem to be trying to use a main C file with a C++ lib. You can use C with C++ but not the other way around.

False

Not applicable at this stage.

Wrong question. How do I know what the value should be or what does the macro do are better question. Answers: It is the default chip clock. Macro is used set timing for some of the builtin functions. Explained in detail here: kzbin.info/www/bejne/e164foKubNapaM0 If you truly want an answers to your question, copied it from prep code.

There is an email on the channel page at more links. Next to logo. Only available on desktop.

kzbin.info/www/bejne/gpjCYWOBi72crbM kzbin.info/www/bejne/r6fGcpyJg5yobqs you'll have a better time looking for SWD (serial wire debug) than for ISP.

kzbin.info/www/bejne/eHnVqnZ8rJeIaZI kzbin.info/aero/PLtuqBdbsL-DvbB6QAGgoGBAEsGuXfGFoF

Nothing really. Most likely I will only duplicate what is already got on here if I decide to use another platform. Thanks sticking around for 3 years. I used to be somewhat active on twitter and patreon a few years back but it was mostly it was directing back to here. Links are in the description it you want to have a look.

Sarcasm?

Get an original st-link-V3 mini ~$10. I used a Segger J-link EDU, it is no longer manufactured. ST does not like people using closes with their software. If you setup a you own tool set the clones work fine. If you want to use ST tools you are going to have to use a Segger or an ordinal ST-Link. If you got a Nucleo you can hijack the ST-link from it.

You seem very distressed. You do not understand because you have never done serious high speed DSP. No-one uses the basic ADC on a STM but you still need to under stand it. The meat and potato's sit with DMA. Zero clock cycles wasted on operating the ADC. Set it and forget it. It will sample in the background. You only need to read the sample data out fast enough. Hands down the best ADCs I have ever used are from ST. Renasa is a close second. "select channel,switch it to sample and hold,start sampling ,give result" Exactly the same for a ST chips when using blocking samples. "Microchip Risk Processors" PIC is horrendous. "inter channel interference is a big issue. Nobody is addressing" This is a you problem. Fix your circuit. You likely have capacitive coupling caused by something external.

Jy het nog nooit silent errors dan al gesien nie. As ek dit kan sien het hy dit gegooi. Toys uit die kot uit op die vloer. "Error vomit" is n ander term wat ek like.

I2C is the main focus of the video. The RTC is just something simple to interface with. A OLED can be a whole video series on its own.

Cause you are using a SAM device. Last time I checked the support for Atmel chips was terrible on MPLAB. Try Microchip-studio (Atmel Studio) kzbin.info/www/bejne/eHnVqnZ8rJeIaZI