CCS/TMS320C5515: NOR Flash issue

Hi Cam,

Sorry about the trouble. To make sure I understand... All of the boards are able to boot from NOR flash, but during the application execution some of the boards cannot read from NOR flash? Is that right, or do some of the board fail to boot from NOR flash sometimes too?

Do you have JTAG access on these boards?

This issue could be caused by many things: bootloader compatibility with the flash, copying code into SARAM31 that is used by the bootloader, device initializtion after boot (during application execution).

One data point to check is the Program Counter after the bootloader has completed. Make sure not to use a GEL file when connecting to the device after the bootloader executes. The GEL file will wipe the state of the device after the bootload.

You should be able to read back the contents of the NOR flash with the programmer after programming the NOR. You should also be able to see the contents of the flash through the mem window in CCS. Look for the valid boot signature of 0x09AA in the first two bytes to verify the boot image was copied correctly (at least the first two bytes).

Refer to the bootloader and programmer resources.

- http://processors.wiki.ti.com/index.php/C5515_Boot-Image_Programmer#How_to_program_a_boot_image_onto_C5515_EVM

- Refer to C5515 Schematic checklist - Section 3.20 Bootloader "NOR Boot: NOR Flash must support the Flash reset command (0x00F0 on data) and return to the read array mode afterwards, NOR Flash should support the common flash memory interface (CFI) (not applicable to C5532/33/34/35 or C5545)"

  We ran into this issue with the Intel P30 NOR flash. It does not support the software reset command, and would repeatedly read the status register instead of reading data from the array.

I checked the SST39VF3201C datasheet and it does not appear to support the reset command. You might just try issueing this command with a test project from CCS to see how the flash responds to the unhandled command.

See the below code excerpt from the bootloader - the reset command is issued at least three times.

Have you checked that your application code can run by itself, without any initializtion performed by the GEL file?

The program should be able to reset all peripherals and initialize the pin mux (EBSR), PLL, EMIF, and any peripheral it needs by itself. Load the program without first running a GEL file from CCS.

Confirm PLL and EMIF are set as they are in the CSL examples.

For the programmer - get it from the latest CSL http://www.ti.com/tool/sprc133 

<INSTALL_PATH>\c55_csl_3.08\utilities\Programmer\c5515

<INSTALL_PATH>\c55_csl_3.08\ccs_v6.x_examples\programmer

Lets get this thing debugged.

Regards,

Mark

=-=-=-=-

// flash "Reset" command
#define FLASH_RESET_CMD1  0x00F0
// flash "Autoselect" command
#define FLASH_AUTOSELECT_CMD1  0x00AA
#define FLASH_AUTOSELECT_CMD2  0x0055
#define FLASH_AUTOSELECT_CMD3  0x0090
//flash program command
#define FLASH_PROGRAM_CMD1  0x00AA
#define FLASH_PROGRAM_CMD2  0x0055
#define FLASH_PROGRAM_CMD3  0x00A0

int flashGetDeviceData(FlashDeviceData_t *Data)

{

  Uint16 Tmp1, Tmp2, Tmp3;

  Uint16 NumEraseBlockRegions;

  Uint16 ReadIndex;

  Uint16 Region;

  int FlashDeviceIndex;

  // flash "Reset" command

  ((volatile unsigned short*)NorFlashBaseAddr)[0] = FLASH_RESET_CMD1;

  // flash "Autoselect" command

  ((volatile unsigned short*)NorFlashBaseAddr)[0x555] = FLASH_AUTOSELECT_CMD1;

  ((volatile unsigned short*)NorFlashBaseAddr)[0x2AA] = FLASH_AUTOSELECT_CMD2;

  ((volatile unsigned short*)NorFlashBaseAddr)[0x555] = FLASH_AUTOSELECT_CMD3;

  // get the manufacturer-id and device-id

  Data->MfrId = *(volatile unsigned short *)NorFlashBaseAddr;

  Data->DevId[0] = *((volatile unsigned short *)NorFlashBaseAddr + 0x1);

  Data->DevId[1] = *((volatile unsigned short *)NorFlashBaseAddr + 0xe);

  Data->DevId[2] = *((volatile unsigned short *)NorFlashBaseAddr + 0xf);

  // flash "Reset" command

  ((volatile unsigned short*)NorFlashBaseAddr)[0] = FLASH_RESET_CMD1;

  // flash "CFI Query" command

  ((volatile unsigned short*)NorFlashBaseAddr)[0x55] = 0x98;

  // verify "QRY"

  Tmp1 = ((volatile unsigned short*)NorFlashBaseAddr)[0x10];

  Tmp2 = ((volatile unsigned short*)NorFlashBaseAddr)[0x11];

  Tmp3 = ((volatile unsigned short*)NorFlashBaseAddr)[0x12];

  if ((Tmp1 == 'Q') && (Tmp2 == 'R') && (Tmp3 == 'Y'))

  {

     // read the number of erase-block regions

     NumEraseBlockRegions = ((volatile unsigned short*)NorFlashBaseAddr)[0x2C];

     if (NumEraseBlockRegions > FLASH_NUM_SECTOR_MAP_ENTRIES)

     {

        ((volatile unsigned short*)NorFlashBaseAddr)[0] = FLASH_RESET_CMD1;

        return FLASH_STATUS_ERROR;

     }

     ReadIndex = 0x2D;

     for (Region=0; Region<NumEraseBlockRegions; Region++)

     {

        // read the number of sectors in the region

        Tmp1 = ((volatile unsigned short*)NorFlashBaseAddr)[ReadIndex+0];

        Tmp2 = ((volatile unsigned short*)NorFlashBaseAddr)[ReadIndex+1];

        Data->SectorMap[Region].NumSectors = (Tmp2 << 8) + (Tmp1 & 0xFF) + 1;

        // read the size of the sectors in the region (words)

        Tmp1 = ((volatile unsigned short*)NorFlashBaseAddr)[ReadIndex+2];

        Tmp2 = ((volatile unsigned short*)NorFlashBaseAddr)[ReadIndex+3];

        Data->SectorMap[Region].SectorSize = ((Tmp2 << 8) + (Tmp1 & 0xFF)) << 7;

        ReadIndex += 4;

     }

     for (; Region<FLASH_NUM_SECTOR_MAP_ENTRIES; Region++)

     {

        Data->SectorMap[Region].NumSectors = 0;

        Data->SectorMap[Region].SectorSize = 0;

     }

     // check device-id to find match in table (needed for some top-boot devices)

     FlashDeviceIndex = flashGetDeviceIndex(Data); // -1 means not found

     if (FlashDeviceIndex >= 0) // if not found, just use data from device

     {

        // Copy the sector-map data (override needed for some top-boot devices).

        // The sector map data is reversed, as read from some top-boot devices.

        for (Region=0; Region<FLASH_NUM_SECTOR_MAP_ENTRIES; Region++)

        {

           Data->SectorMap[Region].NumSectors = FlashDeviceTable[FlashDeviceIndex].SectorMap[Region].NumSectors;

           Data->SectorMap[Region].SectorSize = FlashDeviceTable[FlashDeviceIndex].SectorMap[Region].SectorSize;

        }

     }

  }

  else

  {

     // try to find the device in the flash-device-table

     Data->SectorMap[0].NumSectors = 0; // set to 0 to indicate no erase-block data

     FlashDeviceIndex = flashGetDeviceIndex(Data); // -1 means not found

     if (FlashDeviceIndex < 0)

     {

        ((volatile unsigned short*)NorFlashBaseAddr)[0] = FLASH_RESET_CMD1;

        return FLASH_STATUS_ERROR;

     }

     // copy the sector-map data

     for (Region=0; Region<FLASH_NUM_SECTOR_MAP_ENTRIES; Region++)

     {

        Data->SectorMap[Region].NumSectors = FlashDeviceTable[FlashDeviceIndex].SectorMap[Region].NumSectors;

        Data->SectorMap[Region].SectorSize = FlashDeviceTable[FlashDeviceIndex].SectorMap[Region].SectorSize;

     }

  }

  // flash "Reset" command

  ((volatile unsigned short*)NorFlashBaseAddr)[0] = FLASH_RESET_CMD1;

  return FLASH_STATUS_OK;

}

Hi Mark,

Thanks for the quick reply and I'll go over your info in more detail to see what might be a clue. First, to answer a few of your questions.

All the boards took the programming via JTAG and CCSv7 using programmer_C5515_eZdsp.out. All boards boot up ok and run the application. Most don't read the NOR properly. I have been using CCS to see what is happening and notice the are reading 0s. I did use the memory browser to take a look at address 0x400000 to see the boot code (starting with 09AA) and on a good board I can see the code. On the bad one, the memory browser only shows 0s all the way to the top of memory from what I quickly scrolled through.

I was wondering if my EMIF parameters were incorrect, but it looks like they ok looking at the timing diagrams. Any idea what the parameters for the boot code are?

I'll take a detailed look at your answer and try some more experimentation, but if you have any other thoughts, please fire them my way.

Cheers.

Here is an extra bit if information.

I have a firmware update option in my code that will read from the SD and writes to the lower part of NOR. It works fine running independently without CCS both before and after the update. Obviously the code is successfully writing to NOR but when it gets to other parts of the code where it is suppose to read, it doesn't. Hmmm.

Oh, and I did check and the NOR is CFI compliant and has a 0x0F reset. They just call it a CFI Exit but the text says it does a reset as well. 

Cam,

That's great to hear. Thanks for sharing your solution on the E2E.

Regards,
Mark