Scribd Logo
Upload

Welcome to Scribd!

  • 04 Softdevice Student Introduction v0.1

    Uploaded by

    nngeneralissimo
    7 views13 pages
    The document discusses the architecture of a Nordic Semiconductor SoftDevice and how it interacts with application code. The SoftDevice resides in its own region in program memory and handles Bluetooth Low Energy functionality through system calls. When an application calls a SoftDevice API function, it is expanded to an SVC call that is handled by the SVC_Handler. This switches to the SoftDevice code, which implements the specific functionality. SoftDevice events are notified through an interrupt handler that the application can use to poll for events.

    Original Description:

    Original Title

    04_Softdevice_Student_Introduction_v0.1

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    The document discusses the architecture of a Nordic Semiconductor SoftDevice and how it interacts with application code. The SoftDevice resides in its own region in program memory and handles Bluetooth Low Energy functionality through system calls. When an application calls a SoftDevice API function, it is expanded to an SVC call that is handled by the SVC_Handler. This switches to the SoftDevice code, which implements the specific functionality. SoftDevice events are notified through an interrupt handler that the application can use to poll for events.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    7 views13 pages

    04 Softdevice Student Introduction v0.1

    Uploaded by

    nngeneralissimo
    The document discusses the architecture of a Nordic Semiconductor SoftDevice and how it interacts with application code. The SoftDevice resides in its own region in program memory and handles Bluetooth Low Energy functionality through system calls. When an application calls a SoftDevice API function, it is expanded to an SVC call that is handled by the SVC_Handler. This switches to the SoftDevice code, which implements the specific functionality. SoftDevice events are notified through an interrupt handler that the application can use to poll for events.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    of 13

    •

    •
    •

    •
    •

    •
    •
    •

    •
    Program Memory
    SizeOfProgMem
    RAM
    0x2000 0000 + *MSP initial value -
    Application SizeOfRAM Call Stack
    region

    Application
    region
    CODE_R1_BASE Application Vector Table
    RAM_R1_BASE
    SoftDevice SoftDevice
    region region
    (Binary file from Nordic) 0x2000 0000
    System Vector Table
    0x0000 0000
    // Use the SoftDevice API functions as normal C functions.
    application.c #include "ble_gap.h"
    sd_ble_gap_connect(…);

    // The functions are definitions that expands to SVCs.


    application.h uint32_t __svc(SD_BLE_GAP_CONNECT) sd_ble_gap_connect(…);

    // SoftDevice functions are called from the


    // SVC_Handler interrupt routine.
    void SVC_Handler(int svc_num, int *svc_args)
    {
    softdevice.c switch(svc_number)
    {
    …
    case SD_BLE_GAP_CONNECT:
    sd_ble_gap_connect();
    •

    // SWI2 -> SoftDevice Event Notification


    void SWI2_EGU2_IRQHandler(void)
    {
    // Poll for SoftDevice events.
    }
    ▪
    ▪

    ▪
    ▪
    ▪
    ▪
    ▪
    ▪

    ▪
    ▪
    Priority levels
    •
    •
    •
    •

    •
    •
    •
    •
    •

    •
    •
    ▪ ▪
    ▪ ▪
    ▪ ▪
    ▪ ▪
    ▪
    ▪ ▪
    ▪ ▪
    ▪ ▪
    ▪
    ▪

    You might also like