I just received this little dev board from China (Nano M0) that has an NXP LPC1114/301 on it and it has a built-in SWD I/F that pretends to be a J-Link. Anyways I installed the latest J-Link software and it upgraded the firmware in the pseudo-J-Link and I was able to get the latest eval version of the Keil MDK uVision talking to it and can do everything expected except that the "Registers Window" displays all zeros. I can go into the Segger control panel's "CPU Regs" and even change the registers from uvision and see the change in the Segger control panel but the uvision "Registers Window" continues to be all zeros. Anybody have any idea what I'm doing wrong? Thanks!

After getting my J-Link'd LPC1114/301 dev board unbricked I still see this issue. The J-Link log file shows the registers being properly read but they just aren't getting into the uVision "Registers" window . Memory is being read fine.

I also have other dev boards that do work properly with uVision but they use other emulators. One is a CoLinkEx emulator talking to its attached LPC1114/301 target so I know it's not a problem with the chip type or with uVision. I suspect I have something set wrong in uVision but I can't imagine what? I need to purchase either a "legal" ULINK2 or a J-Link for commercial development and would like to verify that this isn't a J-Link problem interfacing to the LPC1114/301 before I decide which to buy. Thanks!

Nobody has a clue as to what I'm doing wrong or can say they've seen the register display in uVison work with Jlink and an NXP M0 target? I should mention that I can see the peripheral registers just fine. A screen shot showing the problem is attached as well as a copy of jlink.log showing the registers were in fact read even though all zeros was displayed. Very strange? i have tried deleting and reloading both uVision and the J-Link software. The present configuration is with just the uVision installed and the Segger software removed so I'm just using the drivers that ship with uVision. All configurations I've tried result in the same result .


JLink.txt

Nobody has ever seen this? I think this little board is not licensed to use J-Link - is it possible that J-Link is detecting that and "sabotaging" the register read transfer to Keil somehow? No big deal as I've moved on to Nuvoton dev boards using the Nu-Link SWD adapter for the development but I'd rather not have to tell folks that J-Link doesn't work properly with M0 and Keil if this is something stupid I'm doing . We'll be needing to buy some SWD adapters for production in a couple months ...

Thanks!

Thanks, it works great!