Subject: nRF9151 – EU coverage of mfw 2.0.2 and antenna gain (Schréder Sense One)
Dear Nordic
I'm working on CE and RCM certification for Schréder's SENSE ONE smart-city...
We have an nRF54L15 (QFAA) board, acting as an I2C target ( TWIS30, P0.00/P0.01, address 0x42, 100 kHz ) for an ESP32-S3 through a TCA9406 level translator.
Flow:
Between...
Hello, I am requesting a schematic review of my bluetooth microphone system. I've used the spec sheets as well as audio DK hardware reference material to design these schematics...
We are seeing very high defect rate when installing this part on boards: insufficient solder, solder bridging. When we look at the pads under the microscope, we are seeing...
Hello,
We have an issue. Our device is a custom board based on the nRF9151, and we use it in Latvia. Two network providers are available for our Onomondo SIM card: one supports...
Since I wrote about CrossWorks a few weeks ago, several people have mailed me and asked me if I have any sample projects. I didn't, so I just created some.
I've created projects which build blinky_example…
Updated version here (21.04.15): https://devzone.nordicsemi.com/tutorials/7/development-with-gcc-and-eclipse/
I have noticed that there have been several questions on development with Eclipse and GCC…
Atomwear is a micro, modularized, open source, wearable BLE device for DIYers. It makes any BLE(Bluetooth Low Energy) projects easier
Overview - What’s the Atomwear?
Atomwear is a BLE product based…
You may have a nRF51 chip that is "bricked" and both nRFGo Studio and nrfjprog recover option doesn't work. You can try to use J-link Commander to recover. In some case, J-link Commander showed that it…
I created this blog post to document the bugs reported on nRF51 SDK v6.0.0
The workaround for each bug would also be provided here as a temporary solution before the bug is fixed in the future release…
Our most advanced Bluetooth Smart SoftDevice to date is now - S130. We're excited in a big way about this one covering as it does so many different options in one protocol stack.
Again, we always value…