I have already made code of 3 pwm channels using c[0],cc[1],cc[2],cc[3]. I want 4 PWM channels but I dont have more cc registers left so how can i code it. plz help me.
ALso...
Hello, I have purchased this kit on ebay. www.ebay.com/.../301182420397
Can somebody point me to where I can get documentation on this kit, it came in with mostly Chinese...
According to the nRF51 series reference manual.
10.1.2 Debug interface mode
Debug interface mode is initiated by clocking one clock cycle on SWDCLK with SWDIO=1. Due...
Hi,
I was looking at the .map for my project and I noticed that pstorage.c was taking up a bunch of RAM (~600 bytes), which I thought was a lot, so I went into pstrorage_platform...
The document nRF51422_Evaluation_Kit_User_Guide_v2.0.pdf says:
Locate the Heart Rate demo project found in the folder
ARM\Device\Nordic\nrf51422\Board\pca10003\s310\ble_app_hrs...
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…