HW: MK60DX256xxx10 processor with SEGGER JLINK probe running on Ubuntu 12.
My Intent is to erase the FlexNVM area of the chip (start address 0x10000000 - 0x1003FFFF)
I am using JLinkGDBServer on LINUX via the following command line: JLInkGDBServer -x=Nitin.gdb -select -usb=S/N
APPROACH 1: From SEGGER docs it seems straight forward. Inside my Nitin.gdb file I pasted "monitor flash device = MK60DX256xxx10" but that does NOT erase my FlexNVM at all. I dont know what this device selection does then ?
APPROACH 2: Inside Nitin.gdb file, I used the following FlexNVM memory partition code: "monitor MemU8 0x40020007 = 0x80 (selecting Prog Partition mode)monitor MemU8 0x4002000A = 0x32 (EEPROM size 32K)
monitor MemU8 0x4002000B = 0x03 (D-FLASH size 224K)
monitor MemU8 0x40020000 = 0x80 (Execute the partition cmd)
That did NOT work either, I read registers back and it seems flash registers are programmed properly but still FlexNVM is NOT erased.
APPROACH 3: Inside Nitin.gdb file, I used the following Mass Erase: "monitor MemU8 0x40020007 = 0x44monitor MemU8 0x40020000 = 0x80"
It MASS erases the chip, gets what I need but now I get error messages from the JLinkGDBServer saying core is confused because of mass erasing, some registers are not read and hence my loaded program DOES NOT work.
Anybody out there has faced similar situation ?
Idea is to just mass erase (including P-FLASH & FlexNVM) the chip using JLinkGDBServer on Linux without any errors
My Intent is to erase the FlexNVM area of the chip (start address 0x10000000 - 0x1003FFFF)
I am using JLinkGDBServer on LINUX via the following command line: JLInkGDBServer -x=Nitin.gdb -select -usb=S/N
APPROACH 1: From SEGGER docs it seems straight forward. Inside my Nitin.gdb file I pasted "monitor flash device = MK60DX256xxx10" but that does NOT erase my FlexNVM at all. I dont know what this device selection does then ?
APPROACH 2: Inside Nitin.gdb file, I used the following FlexNVM memory partition code: "monitor MemU8 0x40020007 = 0x80 (selecting Prog Partition mode)monitor MemU8 0x4002000A = 0x32 (EEPROM size 32K)
monitor MemU8 0x4002000B = 0x03 (D-FLASH size 224K)
monitor MemU8 0x40020000 = 0x80 (Execute the partition cmd)
That did NOT work either, I read registers back and it seems flash registers are programmed properly but still FlexNVM is NOT erased.
APPROACH 3: Inside Nitin.gdb file, I used the following Mass Erase: "monitor MemU8 0x40020007 = 0x44monitor MemU8 0x40020000 = 0x80"
It MASS erases the chip, gets what I need but now I get error messages from the JLinkGDBServer saying core is confused because of mass erasing, some registers are not read and hence my loaded program DOES NOT work.
Anybody out there has faced similar situation ?
Idea is to just mass erase (including P-FLASH & FlexNVM) the chip using JLinkGDBServer on Linux without any errors