วีดีโอ

This coming off the heels of me just learning to use function pointers is super helpful. It contextualizes use cases really well, and i wish there was a discussion of their applications for the use cases at the end of the video.

I couldn't live without function pointers! Agreed, nowadays I use a language (Forth) which makes it much easier to use function pointers, but I wrote my Forth compiler by basically using three tables - one of which with function pointers using something resembling your second technique.

I thin you misspoke at ~ 6:19, "You don't want these (function pointers) in FLASH...". I think you meant, "You don't want these (function pointers) in RAM...".

The simulation suggestion near the end of the podcast is horribly underrated.

Here is the link to the Edge AI book that you can download for free: edgeimpulse.com/edge-ebook

What a great little vid! Thanks.

Sound amplitude needs to be High to help watching in pc .it is ok in mobile

Function pointers are evil? I have always used them and I never had any problem with them, unless you have a bad memory or stack overflow or damaged memory section then this will never happen, assuming there is an active WDT monitoring those special cases. I have always recommended to use an auxiliary MCU in case the first had damaged memory then the second takes over - in case of medical or security applications.

Fuck AI

Very interesting talk, thank you!

I am an EE with 45 years of embedded retiring soon. All assembler, C, and then C++ OO at several multi-national top tier companies. Started using DevOps at least 10 years ago. STILL SEEING 65% OF PROJECTS OF OUR PROJECTS ARE LATE!! What is different from the old days? 100% of the Tech. What is the same as the old days? 100% of the management strategies.

Awesome! 🎉

@22:40 it would be great if we have translators between assembly codes of various manufacturers that help facilitate the code transition to another manufacturer.

@21:32 for low count pin MCU we can set the code to poll for the zero logic via the switch for 1 second after power up, or so - and after say 1 second from power up the code flow goes automatically to program, not bootloader, if low logic is not detected. So before you power up you just press and hold the switch then power up - this guarantees that the MCU will enter bootloader code. I have done such a similar design before. Then re-use that GPIO pin for another task.

nicely explained this part 49:17

Excellent. I plan to use to resolve issue with FTDI232 board that doesn't seem to like me powering my PCB separately. Unfortunately, I will have to create my own breakout board, but that's a minor inconvenience.

C++ for embedded system? I think he misspoken, first C++ too bloated for an embedded system, with the limited resources available for an embedded system, C will always be the de facto programming language for embedded development and also C will never be faced out, lot of compilers, applications included enterprise applications depend on this ubiquitous language and the most popular programming language of all time. Rust did nothing new in term of technology only help programmer who don't understand C with memory management and allocations and synthetic sugar for using structure as interface the funniest thing is any language new or upcoming will still need to be write in C and with the portability of C and how small it is, it's the perfect language for embedded system and any system applications in my opinion. So instead of trying to look or invent a new tools take the time to understand the one you have and how it works use the good side for your advantage and be aware of the bad ones and take note. We all know the usefulness of an hammer also we also know how dangerous it is during engagement if we don't pay attention so do we say hey the hammer hit me on the finger so it's not good for this function we need another hammer that won't crush my finger when I'm using it even if I wasn't paying attention. No programming language is perfect the same way no software is perfect out of the box so why do we always pretend and justify the proliferation of programming language every time some programmer got bitten by not understanding the tools they're using. Please understand your tools and the functionality of the tools to help your development and help you write elegant codes and software.

So how much time do we have until there won't be any job for embedded programmers in your opinion?

Awesome video. I'm curious, do you have a favorite RTOS to work with?

Great video, thank you!

Great video, gents! I'm a history nut so I loved this.

Max is a legend!

How many decades we have to wait till we get a universal HAL like uart_init(ch) uart_read(ch, u8*) uart_write(ch, buf, len) chip independently, out of the box, which then can be customised.

Thank you, Jacob! Long time no see! Great video. but, sometimes, I feel using ChatGPT is kind of cheating. weird... sigh...

The use cases gives me inspiration to enhance my C code, so a big thank you from me.

How can you get SES attached to the target via J-Link and the SystemView access J-Link at the same time?

Thank you for this free education.

My debugger only has JTAG, i.e. no real-time tracing via Arm's ITM SWV (SWD+SWO) or J-Link RTT. How can Tracealyzer be used, either streaming via uart (USB CDC), or versus placing in ram for later analysis? Would love to see a typical debug session using Eclipse+Tracealyzer and an STM32.

Thank you

Another problem is that calculating the maximum stack usage becomes non-trivial. For each function pointer invocation it has to be clear which functions can potentially be called.

so true, but so difficult to do, constantly.

I just bought your book today.❤

Really nice explanation of the bootloader topic . I had a lot of questions on mind but this cleared up alot

The stops: up. to. date.

Thanks for the demo

Really good video! Thanks for taking the time to make it.

That memory map allocates a whole 1KB page to the boot config byte. You said you write a string there rather than a whole byte, but do you write anything else here? It seems like a waste of a flash page if there isn't much written there.

Great video and explanation! Thanks

What’s the job a developer comes to someone to update their firmware? What’s that guy? If I wanna be him lol

very helpful many thx for sharing

Great Tutorial. Thank for sharing this great overview

Interestingly, I violated the rule that said it should be constant and my code was crashing because it was pointing to the 0x0. As I was debugging the issue, I found out another bug index out range. So one bug exposed another nasty bug. Note that, before implementing function pointer other bug was still there but I couldn't find out because my program haven't crashed or going into hard fault. :D

Very nicely done

best

Exceptional video. Such detailed and clear explanation. Thank you very very much.

do you know what X represents in stack information (X@address )

Great to see you again!!!

Regarding "Make sure function pointers are NOT stored in RAM"... when I register a callback function, isn't that callback function pointer stored in RAM somewhere (e.g., UART0_ISR->function), even if it's done in pre-compiled or auto-generated code?

Great content!

Great video thank u