I am using IAR Embedded Workbench v8.10.1 and attempting to debug my application on a CC2510F32. I have found that ~20% of the memory addresses in XDATA are read back by the CC DEBUGGER as 0x00; however, I can tell from the execution of my code, that the CPU is seeing the proper values in memory.
I attached a scope to the CLK and DAT lines between the CC DEBUGGER and my processor and I can see per the protocol specified in SWRA124 that the CPU is indeed incorrectly reporting the values at those memory addresses as 0x00. Oddly, the memory addresses that get reported as having 0x00 data at them appear to be constant throughout the run and across runs. If I had a shoddy connection between my debugger and board I would have expected the bad data to be random.
I tried adjusting the clock speed of the CC DEBUGGER to "Slow" with no improvement. All my single stepping and breakpoints seem to work well, its just the memory I am reading in XDATA is not coming back to me correctly. Also, I can confirm my application runs just fine with the debugger attached or not attached. At this point I have only used 1 particular CPU, but I will get to testing on other units when I can get my hands on them. However, the my code does seem to run fine on this unit, I just have an issue with the debugger reading XDATA memory.
My CC DEBUGGER reports that it has firmware version 0041.
Has anybody seen this and are there any recommendations. Are there perhaps memory timing settings I can adjust in the CPU on startup?
