Explore >> Select a destination
|
You are here 
|
peanball.net | ||
| | | | |
ciesie.com
|
|
| | | | | You programmed STM32 microcontroller using Nucleo or Discovery boards. That means you used Serial Wire Debug (SWD) for programming/debugging. Now, you are designing a PCB with a STM32 microcontroller on it, which means you have to be able to program it. One solution is uploading the code through a bootloader - a small piece of software, made by ST that has been saved in the protected (read-only) memory of the microcontroller. | |
| | | | |
lenholgate.com
|
|
| | | | | ||
| | | | |
lewisdale.dev
|
|
| | | | | [AI summary] The author reflects on their experience with the first day of Advent of Code, discussing their approach to solving the problem using Rust and a misinterpretation of the question. | |
| | | | |
ashvardanian.com
|
|
| | | David Patterson had recently mentioned that (rephrasing): The programmers may benefit from using complex instruction sets directly, but it is increasingly challenging for compilers to automatically generate them in the right spots. In the last 3-4 years I gave a bunch of talks on the intricacies of SIMD programming, highlighting the divergence in hardware and software design in the past ten years. Chips are becoming bigger and more complicated to add more functionality, but the general-purpose compilers like GCC, LLVM, MSVC and ICC cannot keep up with the pace. Hardly any developer codes in Assembly today, hoping that the compiler will do the heavy lifting. | ||
