• State Not Answered
  • Locked Locked
  • Replies 7 replies
  • Subscribers 62 subscribers
  • Views 3076 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 127371
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

SES 3.3 nRF52DK Blinky - basic newbie issues

Jeff

Installed SES, nRF Go, & SDK.
Programmed s132_nrf52_5.1.0_softdevice.hex

Imported the example. Compiles nrf52832_xxaa_s132 Internal. Launches and gets to memory check

... asked and answered many times. I understand what needs to be done, just not WHERE to do it.

RAM START ADDR 0x20000000 should be adjusted to 0x20001FE8 RAM SIZE should be adjusted to 0x10000

I assume it is in the linker script or project xml, but absolutely no joy.

While I would like to learn all this, it's a tight timeline, an unexpected subtask, and I could use a hand. What I need to accomplish are two things.

  1. peripheral that turns on or off a GPIO like blinky and reports an ADC status in response to a request. It will need to pair on a pushbutton, etc. I thought I had an off the shelf answer, but no joy.

  2. client blinky sort of device taking AT commands and controlling ~3 peripheral blinky+. It will be controlled by a particle based on some sensors. i was only supposed to work the particle and sensors in this project.

Parents
  • 0

    Hi Jeff!

    Take a look at this video, which is a part of our SEGGER Embedded Studio - Getting Started tutorial series on youtube.
    At approximate 4.00 minutes, it explaines how to change the RAM START/SIZE values.

    For creating your application, I suggest that you take a look at some of the examples in our SDK.
    i.e the ble_app_blinky / saadc / ble_app_multilink_central examples.
    If you face any specific problems, you are welcome to post another question here on devzone, and we will do our best to help you.

    Best regards,
    Joakim.

  • 0 in reply to Joakim Jakobsen

    I assume i will need to sleep the peripheral and wake periodically to save power. the application has a wall powered central that monitors an event. On an event it will tell three (typically) peripherals to activate a GPIO. Some time later they will deactivate. if the timer interval is the longest allowed lag between event and action, then I should be OK.

    When peripheral wakes, it should advertise, be claimed by the paired central, connect. When the central connects, it can send any pending state change, then the peripheral can sleep again (as long as the GPIO stays high/low active).

Reply
  • 0 in reply to Joakim Jakobsen

    I assume i will need to sleep the peripheral and wake periodically to save power. the application has a wall powered central that monitors an event. On an event it will tell three (typically) peripherals to activate a GPIO. Some time later they will deactivate. if the timer interval is the longest allowed lag between event and action, then I should be OK.

    When peripheral wakes, it should advertise, be claimed by the paired central, connect. When the central connects, it can send any pending state change, then the peripheral can sleep again (as long as the GPIO stays high/low active).

Children
No Data
Related