CCS/CC3220SF-LAUNCHXL: cc3220 flash memory problem

Hi Taylan,

I tested this simple code with my very complex application and it worked well.

#define FLASH_ADDR      0x10ffe00

void flashWrite(void) {

  long ret;
  unsigned long addr = FLASH_ADDR;
  unsigned long len;
  char data[] = "The quick brown fox jumps over the lazy dog";

  // erase 2kB block
  ret = FlashErase(addr);
  UART_PRINT("FlashErase: %d", ret);
  if (ret != 0) return;

  // len must be a multiple of four
  len = strlen(data);
  len = len + (4 - (len % 4));

  // write data into flash
  ret = FlashProgram((unsigned long*)data, addr, len);
  UART_PRINT("FlashProgram: %d", ret);
}


void flashRead(void) {

   // check if flash is erased
   if (*(char*)FLASH_ADDR == 0xFF) {
     UART_PRINT("NoData");
     return;
   }
   UART_PRINT("ReadFromFlash: %s", (char*)FLASH_ADDR);
}

But be aware that your content inside internal flash will be erased by ROM bootloader in case of change bin ary image. I did not check this but at TRM is written this:

The CC3220SF bootloader, on every exit from power-on or hibernate, checks the integrity of the exiting (and marked-valid) user application image binary on on-chip flash against the auto-generated SHA-1 ofthe image on serial flash, saved during the program and update phase of the on-chip flash. In case of a mismatch, the on-chip flash is mass erased to protect the user application binary.

The CC3220SF bootloader, on every exit from power-on or hibernate, checks the integrity of the exiting (and marked-valid) user application image binary on on-chip flash against the auto-generated SHA-1 of
the image on serial flash, saved during the program and update phase of the on-chip flash. In case of a mismatch, the on-chip flash is mass erased to protect the user application binary.

Jan

Hi,
Thank you for your reply, i think it was a problem about data sizes, now it works ok. And also it doesn't need to call flashErase function for life of the flash memory.

Taylan.