28026 replacing 28027

Emile,

Can you please let us know the REVID of both the parts (28026 and 28027)? Also, how are you programming the flash - plug-in or SDFlash?

This can be determined from the REVID register at 0x883

Regards

Vaish

Emile,

Can you please let us know the REVID of both the parts (28026 and 28027)?

This can be determined from the REVID register at 0x883

Also, how are you programming the flash - plug-in or SDFlash?

Regards

Vaish

Hi Vaish,

Please excuse my ignorance as I am currently a 4th year student and do not know a lot about anything at the moment.

I am using CCstudio V3.3, as bundled with the stick and using F28xx on Chip programming found under the Tools menu.

As far as the REVID is concerned, it typed it in the Watch window and for the 28026, it is 2179.  The 28027 chip has been removed from the board, so i am unable to retrieve the number.  

Regards
Emile 

Emilie,

Please check the contents of the following memory:

I am wondering whether the device is locked, this could be the reason why you not able to load to flash.

Regards,

Manoj

Hi Vaish,

I seem to have mislead you.  The value i gave you has only been converted from hex to decimal.. I apologize.  The correct value is 0x0000;

Hi Manoj

0x003F7FF8 0xFFFF

0x003F7FF9 0xFFFF

0x003F7FFA 0xFFFF

0x003F7FFB 0xFFFF

0x003F7FFC 0xFFFF

0x003F7FFD 0xFFFF

0x003F7FFE 0xFFFF

0x003F7FFF 0xFFFF

By the way, here is the error i receive trying to program to flash.

**** Begin Erase/Program/Verify Operation. ***

Erase/Program/Verify Operation in progress...

Erase operation in progress...

Erase operation was successful.

Program operation in progress...

Program operation was successful.

Verify operation in progress...

Flash API Error #40:

The Verify operation failed.

First Fail Address = 0x003f41fc

Expected Data = 0xfffe

Actual Data = 0xffff

Emilie,

Flash API Error #40 denotes flash verify failure. This is a genuine flash read failure and has nothing to do with your code / program. I would suggest you to try re-program the device again and see whether we get the same error in the same address. If so, you may have to use another device.

Regards,

Manoj

Hi Manoj,

Since 24hours ago, i received the same error and address at least 20 times.  I noticed that I am able to program to RAM, but the MCU doesn't respond as it should.  Example:  I use it to control a 3-phase brushless dc motor with Hall sensors.  No matter if i disable or enable pull up resistors on the GPIO 16-18, it constantly writes out 3.3V.  Even when I use on of the examples.

Let me start at the beginning.  I have Piccolo Control Stick based on the X320 980 F28027PTA, damaged EPWM1 A and B, and then replaced the MCU with a S320 980 F28026PTS.  I also changed the CCS3.3 setup to now use the XDS100 emulator for 28026, instead of 28027.  I have since then tried several combinations, but to no prevail.

I know the two MCUs have the same footprint, but is it possible to replace them like i did?

Regards

Emile

Emilie,

As you said both F28026 PTS and F28027 PTA share the foot print. So, you should be able to swap the MCU like you did. But, unfortunately, the part you swapped seems to have flash failure, so you have to try another device.

Regards,

Manoj

Manoj

Can the faulty flash and the bad behavior, if I can call it that, be linked?

Regards

Emile

Emilie,

Yes, the flash verify error you get is because of faulty flash.

Regards,

Manoj

Manoj,

I am referring to the GPIO pins constantly being pulled high despite of settings.

Regards

Emile

Emilie,

GPIO16-18 cannot contribute to the flash api error #40.

Regards,

Manoj