zephyr VS blackmagic

Hey folks. Anyone out there waiting for BT Auracast? It was announced June 2022, and immediately struck me as must have.

I lost my earbuds, but it seems ridiculous to get a replacement without Auracast, seems like surely if I'm going to make a decent sized purchase like that it needs to support group playing. I want to tune into the radios of other people on the metro or on the bus, want to be able to watch a movie on the plane with someone.

Auracast was announced in June 2022. Anyone else out there struggling with expectations here? I'm really hoping the product announcement season that's right around the corner had a good number of Auracast announcements.

Side note, a ton of it is over my head but it's been so so fun tuning in every once and again to see how Zephyr's Bluetooth Audio work is going. Just wild now much has gone into this! https://github.com/zephyrproject-rtos/zephyr/commits/main/subsys/bluetooth/audio

I am working on adding support for VisionFive 2 in Zephyr RTOS. I have created a device tree by referencing the starfive linux, patches of hifive_unmatched FU740 SoC and patches of BeagleV Starlight.

We are unsure on how to proceed further with this error. We have opened a github discussion regarding the same issue.

Then there are samples. Look through it for anything useful. RC522 uses SPI, so getting that to work would be a good first step.

Hey, I've been trying to build an app with cmake+ninja instead of west to integrate it into a larger build system and everything works correctly except for the final stage where it uses `/usr/bin/llvm-objcopy` instead of the `${CROSS_COMPILE}` one it tries to find here.

Zephyr has a lot of good points, but I really wish it didn't use Kconfig. Getting a working config seems to be mostly a matter of copying an already working example. It might be okay for hardware side of things, but it's a really bad at software/feature dependency.

Set https://docs.zephyrproject.org/latest/build/kconfig/tips.htm... and the issue: https://github.com/zephyrproject-rtos/zephyr/issues/52575. And don't even get me started on trying anything to group options together.

In this thread u/ikravets explained that there hasn't been much demand for Zephyr, which is why they aren't doing anything with it, and in this pull request Zephyr decided to no longer recommend PlatformIO in their documentation.

The answer is always in the source: https://github.com/zephyrproject-rtos/zephyr/blob/bdaac354f4cb0ad91d952c2f6941c16240d84da2/subsys/tracing/tracing_backend_ram.c

This reminds me of the person who came out of nowhere a few years ago and started creating GitHub issue tickets for anything with "black" in the name, calling it racist. The one I saw specifically, was this one for the black magic probe.

https://docs.flipperzero.one/development/hardware/wifi-debugger-module https://github.com/blackmagic-debug/blackmagic

It's telling me that it can't fit the entire file in the rom. How do I fix this? I followed the instructions from this github article and you'd assume that would be correct.

As we can see, during the installation of blackmagic, makepkg will clone and install the blacksphere/blackmagic GitHub repository. However, if we got to https://github.com/blackmagic-debug/blackmagic, we are redirected to https://github.com/blackmagic-debug/blackmagic. The owners of the blacksphere GitHub account have renamed their account to blackmagic-debug.

Could be interesting if support for this was added to the black magic probe https://github.com/blackmagic-debug/blackmagic

Note you may need to recompile the BMP firmware from scratch to use RTT.

If you cant buy one directly, you can also flash the BMP firmware into alternative hardware like a ST LinkV2/black/blue pill board.