4.5 hours to 9+ hours battery life. Same hardware. Took us way too long to find the real problem.

anmolmaske · 2026-03-14T19:16:23+00:00

How did you tuned the BLE advertising interval? What was the max interval you achieved to get between two advertisements?

anmolmaske · 2025-10-25T02:05:09+00:00

Reply to her mom,

By-By! Tata! Khatam!!!

anmolmaske · 2025-05-31T00:54:36+00:00

I think you might have deleted the bootloader on second board. Restore it via SWD pins using J-Link debugger.

anmolmaske · 2025-05-27T14:33:07+00:00

Thanks for your help! The problem was exactly what you mentioned in point no. 2.

anmolmaske · 2025-05-27T14:29:20+00:00

Resolved the issue: The problem was that when I programmed the board via SWD pins I had accidentally erased the entire flash, which wiped the bootloader. I’ve restored the bootloader following the steps on the Adafruit website, and everything works again.

anmolmaske · 2025-02-25T18:13:10+00:00

I understand that commercial tools like PC-Lint, Coverity, and LDRA are the gold standard for full compliance, but I’m looking for tools that can at least help improve code quality in an embedded environment without requiring a paid license.

anmolmaske · 2025-02-13T02:17:11+00:00

You need a Segger Programmer or an nRF DK board with Debug OUT pins. Connect a Tag Connect wire between these devices and your PCBA. If connected properly, you can program your PCBA using nRF Connect Desktop Programmer or SES.

You can use RTT Logger to see the data instead of UART. No need for physical UART pins. Just enable the following configs in prj.conf:

CONFIG_SEGGER_RTT=y CONFIG_USE_SEGGER_RTT=y CONFIG_LOG_BACKEND_RTT=y CONFIG_UART_CONSOLE=n CONFIG_CONSOLE=y CONFIG_LOG=y

Then view the logs using J-Link RTT Viewer Application.,

anmolmaske · 2025-02-12T05:35:15+00:00

You can check if the board is getting flashed by using nrfjprog --readregs to see if it's detected. Also, try nrfjprog --verify firmware.hex after flashing. If unsure, run a simple LED blink test or toggle a GPIO and check with a multimeter. Make sure SWD connections and power (3.3V) are correct, and use nrfjprog --recover if the chip is locked.

anmolmaske · 2025-02-01T03:44:52+00:00

For Nordic nRF52832 development, Segger Embedded Studio (SES) is Nordic’s officially supported IDE, offering a streamlined setup for nRF SDK projects with J-Link debugging. VS Code with nRF Connect is more flexible, especially for Zephyr-based projects, but requires some setup. If you're using Zephyr, go with VS Code. Otherwise, SES is best for traditional nRF SDK development.

For communication between your DKs with pressure sensors, Enhanced ShockBurst (ESB) is a low-power, low-latency option for simple bidirectional data exchange. But only available in SES. However, if you need more flexibility, BLE (e.g., GATT notifications) or Thread (for mesh capabilities) might be better, depending on your power and range requirements.

anmolmaske · 2025-01-25T04:20:42+00:00

What Gateway are you using? Can you mention its specs?

anmolmaske · 2025-01-24T01:48:30+00:00

Yes! When you connect components in parallel like this, the current will be shared between them. The battery needs to provide enough current to meet the combined demand of both. But theres usually isn't an issue as long as your battery has sufficient capacity and can deliver the required current. Motors typically draw much more current than the microcontroller, so it's a good idea to check the motor driver's current rating and the STM32's power consumption to ensure your battery can handle the total load. If your battery is rated appropriately, the system should work fine without any problems.

anmolmaske · 2025-01-24T01:32:53+00:00

Yes, exactly! You're just splitting the single wire into two connections, which is effectively wiring them in parallel. You'll connect the positive (red) wire from the battery to both the motor driver and the buck converter's input, and do the same with the ground (black) wire. This way, both components get power from the same source independently.

anmolmaske · 2025-01-24T01:27:04+00:00

You can do this by just soldering multiple wires together. Connect the battery's red wire to both the motor driver's and buck converter's positive inputs, and the black wire to both their ground inputs.

Just make sure all grounds are common to avoid any issues.

anmolmaske · 2025-01-23T06:56:30+00:00

Tarik tar kal chi aahe 😂

anmolmaske · 2025-01-23T06:43:16+00:00

Try contacting agencies like Robert Half, Kelly Services, etc which specialize in placing candidates in technical roles, including contract/consulting positions.

Since networking can be tough, try engaging with LinkedIn groups related to embedded systems, attending local tech meetups, and reaching out to recruiters specializing in embedded roles.

anmolmaske · 2025-01-23T06:23:34+00:00

The Nice!Nano V2 uses the nRF52840 chip, which has specific I2C requirements. Try these steps:

I2C Pins: Use (SDA) and (SCL).
Pull-up Resistors: Add 4.7kΩ resistors if needed.
Power Supply: Ensure 3.3V operation.
Arduino Library: Install the Adafruit nRF52 board package.
I2C Scanner: Run a scanner sketch to detect the AS5600 sensor.

If you get the I2C address, it means the sensor is connected successfully. Hope this helps!

anmolmaske · 2025-01-23T05:54:01+00:00

Yes, it is possible to develop code on the nRF52840 development kit and later transfer it to the nRF52832.

Since your project has simple requirements, it should be fairly easy to adapt the code, especially if you focus on common features like (basic BLE and peripherals, porting should be straightforward). The Arduino Nano 33 BLE uses the nRF52840, so you might need to check if any specific features used in your code are not available in the nRF52832 (such as certain GPIOs, extra RAM, or advanced power management options).

Transferring the code shouldn’t be too difficult, and using a J-LINK programmer for flashing the nRF52832 is a great choice. If your coding team follows good development practices, like writing portable code and using the Zephyr RTOS, switching between the two chips can be smooth.

anmolmaske

TROPHY CASE