Jump to content
43oh

Program MSP430G2553 with a smaller memory version in compiler


Recommended Posts

I have to ask if someone knows better. If I have MSP430G2553 controller but in CCS I forget to change the settings for controller and there was chosen the G2453, which is the 8KB version of the same controller..does this somehow damage the controller when I program them? They seem to work but I am not sure if this can cause some surprises or failures as it may happen accidentally when using different controllers??

Link to post
Share on other sites

Odd that it programmed without an error due to the incorrect device. I would figure that there shouldn't be any issues, though.

(this may not be clear.... sorry)

The device selection for CCS gives the compiler information to select the device specific header file (which is a big part of information about what modules are available), as well as memory size and layout (so the compiler can do the allocation appropriately and know if there isn't sufficient memory-RAM or code memory- for the build). If you had tried to use a module that isn't available in the 2453 or the build needed more memory than the 2453 has, build would fail (probably). If you didn't, the devices are the same in all meaningful ways (address space, peripheral addresses, and so on. In particular, the code protection and JAG lockout)

 

Apparently, there isn't a check that the device is what was specified.

 

Link to post
Share on other sites
On 1/4/2020 at 5:54 PM, enl said:

Apparently, there isn't a check that the device is what was specified.

Interesting.  My experience with both IAR and CCS is that they refuse to load images to a device when it's different than what the project specifies and they both clearly report it as an error.

Link to post
Share on other sites
4 hours ago, NurseBob said:

My experience with both IAR and CCS is that they refuse to load images to a device when it's different than what the project specifies and they both clearly report it as an error.

This is why I said it is odd, but I have never tried it myself with devices that are so closely related. I don't know if it actually was programmed with the wrong device specified, but I can see no reason there would be damage IF it was programmed this way.

 

 

Link to post
Share on other sites

> This is why I said it is odd, but I have never tried it myself with devices that are so closely related. I don't know if it actually was programmed with the wrong device specified, but I can see no reason there would be damage IF it was programmed this way <

Agreed. Like you, I've never tried with such closely related devices.

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...