Adding custom SW to DSPS Peripheral Mode on Basic Kit

Hi,

I am using the DSPS sample code with the Basic Kit as my starting point and added a few simple lines of code to receive different message types from the phone DSPS app.

The phone sends different message types to the Basic Kit. Below is the code snippets of the function I made code changes in user_sps_scheduler.c to detect the message types:

static void uart_tx_callback(uint8_t res)
{
static uint8_t size=0;
uint8_t *periph_tx_ptr = NULL;
NearEyeProtHdr *hdr = (NearEyeProtHdr *)periph_tx_ptr;

//function gets called from uart transmit isr or application when its not running
switch(res)
{
case UART_STATUS_OK:
//get data and pointer
size = user_periph_pull(&periph_tx_ptr, size);
break;
case UART_STATUS_INIT:
size = user_buffer_read_address(&ble_to_periph_buffer, &periph_tx_ptr, TX_CALLBACK_SIZE);
break;
default:
ASSERT_ERROR(0); //error: callback called from unknown source
}
//if there is data available, send data over periph
if(size > 0)
{
// determine if the data in the periph_tx_ptr is "Text" to be display in QPI
// or actual QPI commands by looking at the message type in the header
switch(hdr->msgType)
{
// this is a text or speech from the phone
case 1:
// this is a phone number or SMS
case 2:
break;
// this is a QPI command to QPI
case 3:
break;
default:
break;
}
// skip the NearEye protocol header which is the first 5 bytes to get to CI msg
// send the CI message over to UART to QPI. For now, we are not going to try
// sending to the particular QPI specified in the protocol header
uart_sps_write(periph_tx_ptr+sizeof(NearEyeProtHdr), size-sizeof(NearEyeProtHdr), &uart_tx_callback);
return;
}

/ /我没有数据n the buffer so the callback is done
callbackbusy = false;
}

neareye_protocol.h file has this content:

#ifndef _NEAREYE_PROTOCOL_H_
#define _NEAREYE_PROTOCOL_H_

typedef struct {
uint8_t msgType;
uint8_t qpiSelect;
uint8_t brdSelect; // not used in current design
uint8_t resv0; // reserve future use
uint8_t resv1; // reserve future use
} NearEyeProtHdr;

#endif // _NEAREYE_PROTOCOL_H_
Keil compiled and built a new hex binary with optimization level set to 0. When I started the debugger and set a break point at line if (size > 0), it hit the break point when a message was sent to . size has a value of 0x10. However, stepping over to the next line of code will skip over this block message detection check and landed in callbackbusy = false;

I have tried a few different ways with no luck. I also tried flashing the modified code thinking when the board came up, it would boot from flash and this is what I will be debugging event though I know for sure that when running the debugger, the debugger will load the code directly into SRAM and execute.

If you know why, please let me know. or if you don't mind, can you check out the code I have really quick with your setup and you will see what I am talking about. Maybe it won't happen for you because you setup environment might be different than mine.

Thanks,
--Khai