• State Verified Answer
  • Locked Locked
  • Replies 1 reply
  • Subscribers 74 subscribers
  • Views 446 views
  • Users 0 members are here
Attachments (1) Download All
Nordic Case Info
  • Case ID: 276925
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Nordic Connect Development Environment for pro-production prototype using Fastnel BT80F

KentOverton

I'm porting a bluetooth app developed on a PCA10040 to a prototype PCB with a Fanstel BT840F.

My development environment is 

      Windows 10

      nRF Connect V3.7.1

      Toolchain version 1.6.1

      Segger IDE V5.50c

I've connected the prototype PCB using a PCA10095 (version 0.11.0) connected as follows

PCB BT840 PIN                                      PCA10095 PIN

VDD (3.2V)                                              P20 VTG

SWDATA                                                  P20 SWDIO

SWCLOCK                                               P20 SWDCLK

GND                                                         P20 GND DETECT and PCA10095 GND

RESET                                                     P20 RESETUsing

Using nRFConnect Programmer (v1.4.11) I can see the NRF52840   - the Programmer log reflects this

07:42:13.618 Using J-Link Software version 6.88
07:42:14.695 Segger serial: 960120203
07:42:14.695 Segger speed: 2000 kHz
07:42:14.696 Segger version: J-Link OB-K22-NordicSemi compiled Jul 2 2021 10:44:28
07:42:14.696 Core probed: 960120203
07:42:14.696 Core RAM: 256KiB
07:42:14.697 Core ROM: 1024KiB in pages of 4KiB
07:42:14.817 Model: NRF52840_xxAA_REV2.

In the Segger IDE I've used 

     File->Open nRFConnect SDK project. 

This is the directory after doing the build.

5355.peripheral_uart.zip

 I build the solution with lot's off warnings surrounding my code, but with no errors.

When I select Debug->GO the object loads appropriately (see below)l

Preparing target for download
Executing Reset script TargetInterface.resetAndStop()
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via AIRCR.SYSRESETREQ.
Downloading ‘zephyr.elf’ to J-Link
Programming 155.3 KB of addresses 00000000 — 00026d53
Programming 2.7 KB of addresses 00026d54 — 00027833
J-Link: Flash download: Bank 0 @ 0x00000000: Skipped. Contents already match
Download successful

The debugger will occasionally then start, but most of the time I see this in the Call Stack Pane.

 

I am at a loss as to how to proceed.

Thanks for your attention.

  • 0

    A Nordic engineer (Jay Tyzzer) responded to my post and asked if my prototype PCB had a 32khz crystal. 

    It does not.

    Using the SES interface I used project->configure nrfsdk project->drivers->hardware clock controller support->nrf clock controller support -> 32khz clock source to change from crystal oscillator to RC oscillator.

    The problem went away and I am now able to begin debugging my .prototype

Related
Terms of service