• State Not Answered
  • Replies 16 replies
  • Subscribers 74 subscribers
  • Views 2588 views
  • Users 0 members are here
Attachments (1) Download All
Nordic Case Info
  • Case ID: 302201
Options

nRF52 & Fanstel EV-BT832F

MikeDale

all BT example projects from web hang down this call string bt_enable -> bt_settings_init -> settings_subsys_init

blinky example runs fine

Parents Reply Children
  • 0 in reply to Jared

    It's not the EV-BT832 board.  The Fanstel hex demos that I've downloaded work fine communicating with Fanstel Anroid apps.  

    Something must be wrong during the build process.

    google link to the build folder. "visual studio setup.pdf" contains screen clips during the build process.  Other pdfs are Fanstel's documents.

    https://drive.google.com/drive/folders/1MifQ6Ty9BDXUtY9lDnEPfiK0oXa_69Ix?usp=share_link

    Update Feb 4- also fails using the nRF52:

    Talked to Nordic's GENE RITTENHOUSE | Rocky Mountain Regional Sales Manager, Americas.  He suggested disconnecting the Fastel board and running the app on the nRF52 development kit.  Did that.

    Same results on where it hangs up (bt_enable).  It is able to printk to the USB port.  The app is resetting every 1/2 sec and sending the reset ASCII message to the USB.

    Hello World example runs fine.

    Thanks for the help

    Mike

  • 0 in reply to MikeDale

    Hi Mike,

    Could you upload the files as a zip here. Either just drag and drop it in the reply box, or use insert->Image/video/file.

    MikeDale said:
    It's not the EV-BT832 board.  The Fanstel hex demos that I've downloaded work fine communicating with Fanstel Anroid apps. 
    MikeDale said:
    the Fanstel EV-BT832F does have a 32k xtal installed on P000 and P001.

    I'm a bit confused, you have a Fanstel EV-BT832F board and a custom board that has a nRF52832, is this correct? 

    And you're not able to run any of our BLE samples on either the Fanstel board or your custom board without it asserting?

    Can you share the schematic for your custom board?

    regards

    Jared 

  • 0 in reply to Jared

    central_uart-20230206T135432Z-001.zip

    NO CUSTOM BOARD 

    Just the nRF52 Development Kit.  Hangs up & resets at  err = bt_enable(NULL)

    Communicates fine with the UART/USB port.

  • 0 in reply to MikeDale

    Hi,

    Which NCS version are you using?

    Can you add CONFIG_RESET_ON_FATAL_ERROR=n to your project config file, this will prevent the program from resetting when it hits an error. The serial log should specify the error causing the program to assert. Can you share the log output?

    regards

    Jared 

  • 0 in reply to Jared

    Not sure what NCS is or serial log

    Visual Code Studio - about

    Version: 1.75.0 (user setup)
    Commit: e2816fe719a4026ffa1ee0189dc89bdfdbafb164
    Date: 2023-02-01T15:23:45.584Z
    Electron: 19.1.9
    Chromium: 102.0.5005.194
    Node.js: 16.14.2
    V8: 10.2.154.23-electron.0
    OS: Windows_NT x64 10.0.22621
    Sandboxed: No

    Output from USB

    Debug Consol:
    JLinkGDBServerCL: SEGGER J-Link GDB Server V7.66a Command Line Version JLinkGDBServerCL: JLinkGDBServerCL: JLinkARM.dll V7.66a (DLL compiled May 19 2022 15:18:08) JLinkGDBServerCL: JLinkGDBServerCL: -----GDB Server start settings----- JLinkGDBServerCL: GDBInit file: none JLinkGDBServerCL: GDB Server Listening port: 58659 JLinkGDBServerCL: SWO raw output listening port: 2332 JLinkGDBServerCL: Terminal I/O port: 2333 JLinkGDBServerCL: Accept remote connection: localhost only JLinkGDBServerCL: Generate logfile: off JLinkGDBServerCL: Verify download: off JLinkGDBServerCL: Init regs on start: off JLinkGDBServerCL: Silent mode: on JLinkGDBServerCL: Single run mode: on JLinkGDBServerCL: Target connection timeout: 0 ms JLinkGDBServerCL: ------J-Link related settings------ JLinkGDBServerCL: J-Link Host interface: USB JLinkGDBServerCL: J-Link script: none JLinkGDBServerCL: J-Link settings file: none JLinkGDBServerCL: ------Target related settings------ JLinkGDBServerCL: Target device: nRF52832_xxAA JLinkGDBServerCL: Target interface: SWD JLinkGDBServerCL: Target interface speed: 12000kHz JLinkGDBServerCL: Target endian: little JLinkGDBServerCL: =thread-group-added,id="i1" =cmd-param-changed,param="pagination",value="off" arch_system_halt (reason=reason@entry=2) at C:/ncs/v2.2.0/zephyr/kernel/fatal.c:32 32 for (;;) { [New Remote target] [New Thread 536880864] [New Thread 536880680] [New Thread 536877408] [New Thread 536878680] [New Thread 536880464] [New Thread 536881048] [New Thread 536877176]
    [Switching to Thread 536880864]
    Thread 3 hit Breakpoint 1, main () at ../src/main.c:562
    562 {
    Execute debugger commands using "-exec <command>", for example "-exec info registers" will list registers in use (when GDB is the debugger)
Related
Terms of service