AnsweredAssumed Answered

0x0 ~0x7FF (1st FLASH sector) is always erased, debugging with USBDM

Question asked by Jei Chou on Dec 6, 2015
Latest reply on Dec 9, 2015 by Jei Chou



I am porting CW10 project to KDS and encounter difficulties when debugging with latest USBDM (V4.12.1.30). Our target is MK10DX128M7.


I have project reside on FlexNVM with interrupt vectors in 0x0~0x400 just like any normal project.   Then, I have another project that is in FLASH, but arranged to avoid using 0x0 ~ 0x7ff (1st FLASH sector) by the linker file:


  m_interrupts          (RX)  : ORIGIN = 0x00001000, LENGTH = 0x00000400

  m_flash_config        (RX)  : ORIGIN = 0x00001400, LENGTH = 0x00000010

  m_text                (RX)  : ORIGIN = 0x00001410, LENGTH = 0x0001EBF0


This arrangement works in CW V10 using USBDM.   But doesn't work in KDS using USBDM.   After code is downloaded, it is obvious that problem is due to 0x0 ~ 0x7FF being erased, even I have selected "Selective Erase (by sector)".


Is there a work-around?   Thanks!