With all these UF2 first boards the first thing I do is solder on the SWD header and figure out what magic sequence of memory read/writes I need to make over jlink to unlock the flash and remove the damn bootloader.
Sometimes I wonder if anyone actually uses a debugger anymore :(
Over a year ago http://grep.app showed up which does basically all I want from GitHub search and Nat (GitHub CEO) said lets talk, but nothing public happend. Biggest thing I use it for is looking for examples of how to use some API, so exact search of the function name and filter by language. The regex is also super nice to have when I need it.
I had a contact show up with a super old name that I wanted to update but it was right in all my other apps. Turns out I still had the old name in one of the read only merged contacts from WhatsApp (contact showed up fine in WhatsApp). I had to remove my WhatsApp account clear the app data for signal and resync everything.
You can already do a lot with https://renode.io I have run a full simulation with a verilator (slooow) of a small RISC-V before I had hardware in hand.
So many years of people telling me that my exact setup does not work, yet here I am not remembering the last time I had an issue with displays on Linux. It has even gotten _better_ since I moved to Wayland which I am also told does not work.
Except that even studies by the US Department of Justice show that risk of financial loss has one of the lowest impacts on likely to appear in court. This is also not recent discovery, this was heavily researched in the 70s.
Ironically just releasing people as soon as possible actually has one of the largest impacts on making sure people show.
Right URLs never change. Remember when one of the most popular golang logging libraries renamed from github.com/Sirupsen/logrus to github.com/sirupsen/logrus and all of a sudden everything would break because you were using both via some dep vendor.
Or Java where you get 80 char of namespaces that may or may not change because the library moved to be an eclipse project.
I would have agreed with you at one point, but most of the automotive companies are diving into this. They want less computers and would rather invest in hardware partitioning if needed.
BWM has said point blank all of the software in the car will be running Linux.
You can also get with some more work the much higher resolution HIRT images from the GOES sats. It's kind or fun to mess with. I used it as an excuse to mess with offloading the error correction to an FPGA, which was fun but also totally unnecessary.
BLE mesh is difficult to do at high performance across multiple platforms and we did it years before there was a spec. Would I use the spec now? Probably. Would I have waited 3 years for the spec to come out? No.
At the time you could lock up Android devices just by sending too many beacons and require users to factory reset there network settings.
When people say Bluetooth is easy I assume they have not done much more than GATT connections and a simple beacon.
We wrote a Bluetooth mesh product before there was Bluetooth mesh standard. Don't call me lazy for not publishing a short spec when the actual Bluetooth spec is over 100 pages. BLE is "easy" managing a mesh network with transactions , droped packets, authentication, 100s of settings across different products is not. Instead we focused on the product we were trying to sell and things people actually bought based on like Alexa and Google support. We had lots of internal docs that heavily documented things including things that would damage the performance of the network and experiments that failed in practice.
This kind of response is a big part of why I have given up building commercial IoT products for now. It's great to want to have some super abstract high level self discovering protocol, but when you actually start to build on it it really hampers the product.
If you want to build a smart light switch you are trying to get the response time very low and worry about things like syncing behavior around the network. Doing these things ends up being very domain specific and you do creative engineering to make it happen. These are very different than the requirements for say a vacuum cleaner.
Then we have standards that come out like Bluetooth mesh or HomeKit that say this is exactly how a light switch should work. Great, except your light switch has this cool feature that Philips did not think of in the committee meeting and now you are forcing it in and your product once again suffers.
These standards all suck, some small percentage of your customers want custom access (rightfully so), and a large percentage are comparing you on price and experience. The outcome is a closed off product. With maybe a cloud API.
Like I said this is why I don't want to work on these products anymore. You cannot win.
I don't get why people are OK with a company being able to wipe a personal device on a whim. If you want full control of my mobile, then provide a mobile.
If you are interested in a framework for stitching together a soft SoC there is a great framework call FuseSOC. It supports several of the cores used here. :
https://fusesoc.net/
If you tell it to _navigate_ home it will actually pull up the directions and the go button will have a autostart timer so you don't touch anything. Ask for directions and you will have to start touching the screen.
First think I had to do was see if Active Desktop worked... And yes it does. "View My Active Desktop as a web page", I guess Windows 98 was just ahead of its time.
Sometimes I wonder if anyone actually uses a debugger anymore :(