CC2640: Debugging during OAD CC2640 custom board

THERE IS ACTIVITY ON THE MISO/ MOSI AS PROVEN ON THE SCOPE.

Why are you assuming there is no activity?

Can there be a more insightful response?

HOW TO SET BREAKPOINT DURING OAD? NO ONE IS ANSWERING THIS QUESTION.

I meant to say the only active SPI CS. In recent threads, I was having multiple SPI

chip selects. I would have definitely reported no activity on MOSI/MISO had I not

seen any.

I have the debugging information suggested.

• At initial glance, the sniffer logs don't seem different for the out of the box demo

   and the custom board (logs attached).

• The custom board responded to a breakpoint at oadBlkNum++ in the following

             section in oad.c pasted below.

            The out of the box demo never halted at this breakpoint though the debugger

             showed this breakpoint was active.

• The scope picture for the out of the box demo shows no activity on the MISO pin,

            whereas the custom board does. The custom board pin default definition is different.

            Changing this default value in the custom board did not change the MISO pin activity

            on the scope during OAD.

Not sure if this experiment revealed anything. Let me know what you think. The custom board

seems to have trouble in the very end of the OAD.

Thank you,

Priya

const PIN_Config BoardGpioInitTable[] = {

Board_SPI0_MISO   | PIN_INPUT_EN | PIN_PULLUP | PIN_HYSTERESIS,

void OAD_imgBlockWrite(uint16_t connHandle, uint8_t *pValue)

{

 // N.B. This must be left volatile.

 volatile uint16_t blkNum = BUILD_UINT16(pValue[0], pValue[1]);

 // Check that this is the expected block number.

 if (oadBlkNum == blkNum)

 {

   // Write a 16 byte block to Flash.

   OADTarget_writeFlash(imagePage, (blkNum * OAD_BLOCK_SIZE), pValue+2,

                        OAD_BLOCK_SIZE);

   // Increment received block count.

   oadBlkNum++;

 }

 else

snifferLogCustomBoardOAD.psdSnifferLogOADLP.psd