• State Not Answered
  • Replies 3 replies
  • Subscribers 62 subscribers
  • Views 1605 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 112038
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Debug deadbeef using SES

Bee

Hi, everyone. I'm focusing on SES with OS X for a long time. But there are always some faults and I have never succeeded utill now. I used to think OS X made these faults. Finally, I found a Windows PC, and followed the post Michael Dietz write step by step. However, the faults still appeared as shown in the picture: image description If I press the "GO" button, it will be like this. I don't know why.

Maybe reason is:

  1. I'm using a board I drew by myself. But it's the same with the datasheet and is OK with Keil.
  2. I'm using nRF51822-G0 not H0 with 10.0.0 SDK.
  3. I set FLASH_START=0x18000, SRAM_START=0x20002000. Is it right about nRF51?

Is there any other reason can lead to these faults?

  • 0

    Hey,

    A few things changed with Embedded Studio v2.16 from last tutorial. I have updated the blog post: devzone.nordicsemi.com/.../. Please read my comment at the bottom to see which sections have been modified and you should look at.

    This looks like a strange problem. Kind of looks like the softdevice isn't being properly flashed. Maybe double check that it is. I think it could be the app entry point (see updated blog post) and mine and RK's comments.

    If updated blog doesn't fix this please give me some more details so we can figure this out.

  • 0 in reply to Michael Dietz

    Thank you for your reminder. I've found that the fault is caused by downloading ".hex files", so s110 can't be downloaded to the flash. (But I can download the project without s110. ) But why can't I download any hex files with SES? Is it caused by porperty set errors? I promiss I followed that post strictly. Or is it caused by circuit errors? I didn't add pull-up resistors on SWDIO and SWDCLK. Or flash/ram size set error? Or other maybe reasons?

  • 0 in reply to Michael Dietz

    Hello, Michael. I think I've found some potential reasons. I gave up SES and try to use eclipse and gcc to make it work. However, eclipse met the same problem. Then I bought a new nRF51-DK. It works!!! Maybe the nRF51-DK has a different circuit for nRF51422, or the J-Link on the nRF51-DK is defferent from mine.

Related