• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 79 subscribers
  • Views 1065 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Error detecting the target device during debugging session using MSPFET430UIF and IAR Embedded Workbench

Marc Ferrer
Prodigy 50 points

Other Parts Discussed in Thread: MSP430F2617, MSP430F2618

Hello everybody,

this is my first post in here altough I have been checking it very often and it was very useful mostly of times. If the way I will describe my trouble is not right, please feel free to add any comment so that I can do it better next time.

As the title describes, I have got some trouble when detecting the target device of my board during debugging sessions. My target board has a MSP430F2617 and during debugging sessions the target device that IAR recognise is MSP430F2618.

I do not really now if the problem comes from IAR workbench or the debugger tool I use, the MSPFET430UIF. After searching what could be the reasons of that error I have really tried everything I could. Maybe I was not able to see the obvious solution.

The target board comes already with a software running on it, which has been previously debugged and tested successfully with no troubles using the same versions I do, so it is not a point of HW or SW design.

I use IAR (I have tried both v5.20.1 and the latest update from IAR v5.20.4) and MSPFET430UIF (interface dll version 2.4.7.1 and tried also with the latest 2.4.8.2). I have also installed everything in different computers, two laptops (running OS win7-64 and winXP+SP3) and a desktop computer(winXP+SP3).

I set up the MSP430F2617 in all project setting of IAR and the debugger tool as well. I have got no troubles when compiling and writing the program on the flash, even the debug session started, but in the "debug log window" shows that the target device detected is the wrong one (MSP430F2618 instead of MSP430F2617).

I do not know if I should follow programming the code ignoring that point or not, so any idea about the question will be welcomme,

thanks in advance,

Marc

  • 0
    Guru 227245 points

    Form the numbering, I guess that the 2618 is a superset of the 2617 which probably has more ram or flash but else is identical. (I don't have access to my datasheets right now, but you should have a copy to check it)

    If this is true, and the program ha sbeen properly linked for the 2617, you should be able to upload the code and run it properly, even if the FET detects the chip as 2618. It doesn't matter whether the debugger assumes that there is more (but unused) ram or flash than there really is.

  • 0 in reply to Jens-Michael Gross
    Prodigy 50 points

    Exactly, the only difference I could find between both was the size for the main code in the flash.

    As you have pointed out, I'm able to upload the code and to run it. I was wondering if there would be any problem in case the code tried to write in that "extra" part of memory that the FET was, in some way, taking into account.

    If I will not have any trouble if I select 2617 in my project settings, despite the FET detects 2618, everything clear then.

    Thank you for your fast and efficient reply.

     

     

  • 0 in reply to Marc Ferrer
    Guru 227245 points

    Marc Ferrer said:
    I was wondering if there would be any problem in case the code tried to write in that "extra" part of memory that the FET was, in some way, taking into account.

    No. The FET won't access any flash unless the linker has put code there. So as long as teh compiler/linker have built the program for the smaller flash memory, it doesn' t matter.

**Attention** This is a public forum