• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 81 subscribers
  • Views 885 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.

BSL Access under v5

Joe Baird
Prodigy 155 points

I upgrade CCS to v5 and tried load a modified version of the BSL into a MSP430 but I am receiving “MSP430: Trouble Writing Memory Block at 0x1010 on Page 0 of Length 0x4: Could not perform access, BSL memory segments are protected”

The BSL worked fine under v4 and I’ve tried a different chip just to make sure the fuse wasn’t set. I was able to dig through the settings to find the “Allow Read/Write/Erase access to BSL memory” but that still does not work. Are there any other new options in v5 that need to be changed to allow this?

  • 0
    Prodigy 155 points

    Not sure why this got moved from CCS forum as this doesn't seem to be a chip issue (I could program the chips just fine with CCS v4). 

    I've verified that the NRST and TEST pins are being triggered correctly and even tried a fresh out of the package chip.

    Has anyone else had success with CCSv5 programming the BSL?

    Thanks

  • 0 in reply to Joe Baird
    Guru 227245 points

    Indeed, it looks like the "unprotect BSL area" settings are no longer working. Then the error message is of course correct :)
    If it works with CCS V4 on the same chip, then it definitely isn't an MSP hardware problem.

  • 0
    Intellectual 450 points

    Check your dll version (right-click, properties,details). Probably you upgraded your emulator's firmware as recommended by your IDE. I had the same problem when I used the latest Elprotronic's Lite Fet-Pro430, that uses a MSP430v3 dll.

    I'm not sure, but it seems that the new MSP430v3 is bugged in respect to writing to BSL.

    You can try to downgrade your emulator to a MSP430v2 using TI tools from MSP430 developer package and use an old msp430.dll, as I did.

  • 0 in reply to Alexandre Hagihara
    Prodigy 155 points

    Thanks Alexandre, 

    I feel that down grading to the previous version is a good work around, but I'm hoping someone at TI actually sees this and comes out with a fix.

    Is there anywhere to post bugs besides the forums?

  • 0 in reply to Joe Baird
    Genius 4925 points

    Not that I'm aware of - the bug tracker has only a guest access so you can see what happened to your bug (if someone provided you a tracker ID).

    Maybe you can contact Markus - or leave a message in the announcement thread of the MSP430.DLLv3 - it could be that Markus has a subscription to that thread and reacts faster that way.

    So that adds another issue to the v3 - the other I know of is more of an inconvenience (clock cycle counter not working), but this one is a serious flaw. If TI was aware of this, I think it was a rather fast move to release and basically enforce the use of v3 with CCSv5.1 and other third party tools as well.

    Maybe Katie will also look into this - she's also replying quite often to problem concerning the different MSP430.DLLs. 

  • 0
    Prodigy 20 points

    open project properties. Debug->MSP430 Properties, select "Erase main, information and protected information memory" and "Allow Read/Write/Erase access to BSL memory"

  • 0 in reply to Daniel Yoo
    Prodigy 155 points

    Thanks Daniel for reminding me that I haven't closed on this issue. Those were the settings I had tried, and had worked in v4. Since opening this thread I had received a CCS update from TI that fixed other issues (particularly sprintf bugs). I hadn't tried the BSL programming until today and it now seems to work.

**Attention** This is a public forum