SPI example: Application doesn't toggle LED

[Christoph_I]

Hey guys,

I'm working with the Laird DVK-BL652 and the Nordic SDK v.14.2.0 with Eclipse (Kepler) and try the example "SPI Master". I didn't modify this example but after compiling and flashing the application doesn't toggle LED... I think the application doesn't execute SPI transactions.? Can someone help please?

Thanks in advance,

Christoph

[Mojo]

Are pins mapped to the correct IO ? The examples are made for the Nordic DevKit.  IO pins map might be different.  

Eclipse Kepler is quite old too.  Follow this blog to get you updated with latest Eclipse and SDK 16. 

https://embeddedsoftdev.blogspot.com/p/ehal-nrf51.html

https://embeddedsoftdev.blogspot.com/p/eclipse.html

[Christoph_I]

Hey Mojo,

thanks for your answer. You are right. I don't think the LED on the Nordic DevKit needs to be configured or something in this way. Now I have manually integrated a LED from the board into the program and it works. My LED blinks after each transaction.

Eclipse Kepler: I bought this board (DVK-BL652-SA https://www.lairdconnect.com/wireless-modules/bluetooth-modules/bluetooth-5-modules/bl652-series-bluetooth-v5-nfc) and on the manufacturers side is only this instruction (https://www.mouser.de/datasheet/2/986/BL652_Dev_Kit_User_Guide-1591025.pdf) which recommends Eclipse Kepler and Nordic SDK v.14.0.0. What do you think about it?

SPI example:

Do you know which register is adressed in the last line? I can't find it in LIS3DH-Datasheet (accelerometer).

"

//MOD BLOCK FOR NEW REG

static uint8_t       m_config_buf1[] = {0x20,0x97};   //CTRL_REG1: 9 = normal power mode (1.344kHz), Low-power Mode (5.376kHz); 7 = Z-,Y-,X-axis enable
static uint8_t       m_config_buf2[] = {0x23,0x88};   //CTRL_REG4: 8 = output registers not updated until MSB and LSB reading; 8 = high-resolution output mode enabled
static uint8_t       m_config_buf3[] = {0x22,0x10};   //CTRL_REG3: 1 = ZYXDA interrupt on INT1 enable
static uint8_t       m_config_buf4[] = {0x1F,0x80};   //TEMP_CFG_REG: 8 = ADC enabled
static uint8_t       m_config_buf5[] = {0x23,0x88};   //CTRL_REG4: 8 = output registers not updated until MSB and LSB reading; 8 = high-resolution output mode enabled
static uint8_t       m_config_buf6[] = {0xA3,0x00};  //???

"

Best regards,

Christoph

[Amanda Hsieh]

Hi, 

The latest question is far away from the subject. Please create a new support case.

Please also verify the answer to this subject.  

Thanks. 

-Amanda H.

[Christoph_I]

Hey Amanda,

I will create a new support case.

Have a nice weekend.

Best regards,

Christoph

[Mojo]

Well, things evolves very quickly in tech.  What we put on the web yesterday got out dated tomorrow.  SDK14 does not have full support of Bluetooth 5 yet.  Since you are just starting, it would be recommended to start with the latest SDK.  Because by the time you get used to it, you are already outdated.  So if you started with something already over 2 years old, you know....    

[Christoph_I]

Hey Mojo,
I will stick to my version for now, but I will keep it on my mind. What also helped was to switch from Eclipse Kepler to SES (Segger Embedded Studio). As a result, many crazy errors have disappeared.

Have a nice sunday evening.

Christoph

[Mojo]

There are to type of error indicator in Eclipse.  One is from the IDE indexer which parse the code.  This works well if you have a native Eclipse projet not makefile type.  The other errors are the actual project compilation errors which are in the build console when you build.  Those are the real errors. 

BTW. SES uses GCC compiler version 8 and stripped out C++ supports.