• State Verified Answer
  • Replies 9 replies
  • Subscribers 75 subscribers
  • Views 2008 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 269733
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Help getting the PCA20041 Gaming Mouse demo programmed and working

Glen M

Hi,

I've got the gaming mouse dev kit and I'm stuck trying to get it programmed using my nRF52840-DK. See my hardware connection image below. 

If I leave the mouse power switch off, then it seems to just program the dev kit's onboard processor and not my mouse. If I turn on the mouse power switch I get a "no idcode detected" popup. I tried flipping the debug adapter thing that plugs into the mouse over and I got the same behavior. Any ideas?

I may also have a problem with my project as this is the first time I've used Zephyr - but at the very least I think I should be getting to the point of erasing the mouse so that it doesn't work anymore - but it's still got its factory programming on it (I attempted to customize the project in a recognizable way by changing CONFIG_BT_DEVICE_NAME in autoconf.h... hopefully that's the right way to do that)

Thanks,

Glen

 

Parents
  • 0

    Hi Sigurd,

    Yes I just tried again, making sure to get the debug board fully inserted into the connector - no change.

    It seems like it's connected enough for the dev kit to think something is plugged in downstream that needs programming - because if I just unplug the connection to the mouse from the dev kit then the programmer tries to program the nrf52840 on the devkit - but something just won't let the software connect. I also tried using J-Flash V6.92 to connect and it popped up some message about the security bit on the target being set and that if I proceeded to disable the security setting it would erase the target, but when I said OK it failed to do anything and the mouse still has its factory programming.

  • +1 in reply to Glen M

    Hi,

    I think this might be caused by a mismatch between the VDD level the DK uses vs the VDD level the gaming mouse uses.

    If you have a stand-alone Jlink debugger, you should try to use that. 

    Alternatively, you could try to insert another USB cable at "nRF USB" on the DK, and set the nRF power source switch(SW9) to USB, it might be possible to program the mouse then. https://infocenter.nordicsemi.com/topic/ug_nrf52840_dk/UG/dk/hw_debug_out.html

Reply Children
Related
Terms of service