This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

F28M36P63C2: Unable to program either core

Part Number: F28M36P63C2

I have a board with a replaced F28M36P63C2WTT MCU on it that is refusing to program. I'm getting a data verification error, and I'm trying to determine if the chip was damaged in replacement or requires some initialization of the flash before it allows programming.

1. The code and gel file are working on a known good board, I can program successfully on a different board that has already been programmed before. I unfortunately do not have any other blank boards to test this on besides my repaired one.

2. I've read through the data verification errors FAQ and verified that the gel file is correct.

3. I can connect to both cores with no issues. I can use the memory browser and look at the memory. I tried modifying the gel file and setting the memory map to r/w on everything, that didn't help with programming. I tried disabling all verification, and while the error went away the chip didn't program correctly.

4. Using the on-chip flash commands, I get the message "Target is not connected or does not support current Flash operation." This occurs for every command in that menu, including all of the unlock commands. I don't think it's locked, because the area where the locks are in the memory browser show FFFFFFF (or at least the first few I hand checked).

5. I did try fully erasing the flash on my good board and reprogramming it, that worked as well. This leads me to believe that there's either a blank chip initialization step or the chip is damaged.

How likely is it that we could've damaged only the flash portion of the IC when we replaced it on our board? Are there any other checks I can do on the memory to verify if it's bad? Is there some blank chip initialization step I've missed somewhere?

  • As a follow up, I have a second repaired board that has an identical issue. It's unlikely that both boards were damaged in the same way, as on the 2nd board I hand soldered onto the BGA only the programming, boot, power, and ground pins and left all of the IO disconnected.

  • Chris,

    Which CCS version are you using?

    Did you change any of the default settings in the CCS On-Chip Flash GUI?

    Thanks and regards,
    Vamsi

  • I'm using CCSv6.

    By the "on-chip flash GUI" do you mean the settings in the target configuration file under flash settings? I've mucked around with most of the options there, blank check, verify, auto ECC generation, etc. One thing of note is that the board that successfully programmed is from 2015, and the repaired one has a recently purchased IC. Specifically, old chip is rev B of the silicon, new chip that doesn't program is rev F.

  • Chris,

    Could you update to CCSv8.x or CCSv9.x?  We recommend CCSv8.3.1 for 32-bit Windows systems and CCSv9.x or higher for 64-bit Windows systems.

    That should help fix this.

    I don't think your chip is damaged.

    OnChip Flash GUI is available at CCS Debug window -> Tools -> On-Chip Flash.

    Let me know if moving to CCS8/9 helps.

    Thanks and regards,

    Vamsi

  • Vamsi,

    This fixed it! CCSv9.2.0 allowed me to program both cores. I assume the updated flash tools were required for the newer revision of the IC. It would be nice if the errata for the chip revisions listed what version was required instead of just generically saying "updated flash tools". But, nonetheless, happy my chip isn't broken.

    Thanks for your assistance,

    Chris