

Nope, I don’t know the difference really. I think my arch distrobox had code oss marketplace extension as a package (to get nrfconnect auto updating) so maybe that’s the reason?
Nope, I don’t know the difference really. I think my arch distrobox had code oss marketplace extension as a package (to get nrfconnect auto updating) so maybe that’s the reason?
I use Code OSS with clangd and the nvim extension (because Microsoft disabled their c/c++ tools) because i want access to the nrfconnect extension pack as a beginner. I don’t have to go searching in the documentation and compiling, then recompiling 10 times to self-discover the required devicetree parameters and figure out what drivers are available vs mainline zephyr.
Plus the debug interface works well.
For everything else possible it is vim/neovim, but I haven’t been able to find good neovim setup for nrfconnect.
Hmmm, I used littlefs for SD card writing at work with an STM32F0 chip. It was hell working with files when tons of essential functions like appending and seeking simply didn’t work in the STM HAL… Plus dealing with opening and closing files and appending files and having to seek in them to find what you want, parsing results, cleaning old files, etc… compared to simple circular buffer and a start and end address of relevant data that can be erased once every day or week depending on use. Even with a daily erase of the NOR chip, they are rated for 100k program/erase cycles which would be over 250 years before degradation starts. I am not dealing with a ton of data nor the flexibility of a full UI/ app storage where I would definitely just use littlefs.
This is literally every train in Belgium, I’m pretty sure it has been for a long time. We are anti-social