• Join
  • Sign In with my.TI Login
Texas Instruments
  • Products
  • Applications
  • Tools & Software
  • Support & Community
  • Sample & Buy
  • About TI
Sample & Purchase Cart Sample & Purchase Cart
  • Search
  • Advanced
TI E2E™ Community
  • Support Forums
  • Blogs
  • Groups
  • Videos
  • 简体中文
  • More ...
TI Home » TI E2E Community » Support Forums » Microcontrollers » MSP430™ Microcontrollers » MSP430 Ultra-Low Power 16-bit Microcontroller Forum » BSL_Scripter-MSP430f5435-CP2102 usb2uart module
Share
MSP430™ Microcontrollers
  • Forum
  • Announcements
  • E2E Wiki
Options
  • Subscribe via RSS
MSP430 Resources
  • MSP430 Product Folder
  • MSP-EXP430G2 - MSP430 LaunchPad Value Line Development kit
  • MSP430 Getting Started Guide
  • MSP430 Microcontroller Projects
  • More Resources >
  • BSL_Scripter-MSP430f5435-CP2102 usb2uart module

    BSL_Scripter-MSP430f5435-CP2102 usb2uart module

    This question is answered
    Kailash V
    Posted by Kailash V
    on Aug 06 2012 02:16 AM
    Prodigy170 points

    Hi,

    I am using CP2102 based usb2uart module to program MSP430f5435 using BSL_Scripter.exe. But I am experiencing few strange situations. I have been able to communicate between the PC and the MSP using the above module. But when i connect the same module to program the msp using cmd I am getting errors. The connections as given below:

    usb2uart  MSP430

    TX                 TA0.1

    RX                 TA0.0

    DTR               RST/NMI

    RTS               TEST

    VCC                  VCC

    GND               GND.

    I have just connected the things and in cmd executing the BSL_Scripter.exe filename.txt . Do i need to do anything explicitly to invoke the BSL..?? I assume just by executing the above command in cmd will invoke the BSL and dumps the code to flash memory of msp.

    The snapshot of the error looks like below:

    And the code in the script.txt is

    MODE 543x_family COM14
    MASS_ERASE
    DELAY 1000
    RX_PASSWORD
    RX_DATA_BLOCK passb.txt

    Also when i change COM14 to USB in cmd its not showing any error. Even when nothin is connected to the PC.

    So can someone please identify where am i going wrong..??

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    All Replies
    • Mo.
      Posted by Mo.
      on Aug 06 2012 07:55 AM
      Genius10960 points

      Kailash,

      you can check the Launchpad-Based MSP430 UART BSL Interface (Rev. A)  App note for more details on the BSL Hardware connection to the Target device.

      http://www.ti.com/mcu/docs/litabsmultiplefilelist.tsp?sectionId=96&tabId=1502&literatureNumber=slaa535a&docCategoryId=1&familyId=342

      Hope this helps, otherwise please let me know.

      BR,

      Mo.

      Make The Switch to TI MCUs

      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • Kailash V
      Posted by Kailash V
      on Aug 06 2012 23:55 PM
      Prodigy170 points

      The connections are correct and I ve referred to that document also. Still the staus of the problem I ve posted remains the same. 

      Regards,

      Kailash

      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • Mo.
      Posted by Mo.
      on Aug 07 2012 04:52 AM
      Genius10960 points

      Kailash V
      I assume just by executing the above command in cmd will invoke the BSL and dumps the code to flash memory of msp.

      Yes, this is correct. The BSL scripter will automaticaly generate the BSL entry sequence to invoke the BSL.

      Can you try it with the below settings?

      MODE 5xx COM14
      VERBOSE
      MASS_ERASE
      RX_PASSWORD
      RX_DATA_BLOCK passb.txt
      DELAY 2000

      Also, what is the Vcc voltage level?

      On the usb2uart module, are you able to see the BSL entry sequence on a scope (DTR and RTS lines) when runing the BSL scripter?

      BR,

      Mo.

      Make The Switch to TI MCUs

      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • Kailash V
      Posted by Kailash V
      on Aug 07 2012 05:07 AM
      Prodigy170 points

      As I am using MSP430f5435 I think MODE should be 543x_family. 

      Vcc Voltage is 3.3V and is there any other way to check the signal in DTR and RTS lines. Becuase i don't have an oscilloscope right now. 

      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • Kailash V
      Posted by Kailash V
      on Aug 07 2012 05:15 AM
      Prodigy170 points

      when i used verbose the cmd looked like this:

      I ve studied about verbose but did not understand properly. Can you tell in breif about that?

      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • Kailash V
      Posted by Kailash V
      on Aug 07 2012 05:51 AM
      Prodigy170 points

      when nothing is connected to the laptop and when the code is executed the above screenshot itself is displayed in cmd..?? how is this possible?

      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • Leo Hendrawan
      Posted by Leo Hendrawan
      on Aug 07 2012 06:18 AM
      Verified Answer
      Verified by Kailash V
      Mastermind28725 points

      Hi Kailash,

      Kailash V

      when nothing is connected to the laptop and when the code is executed the above screenshot itself is displayed in cmd..?? how is this possible?

       
      Because what you see is basically the data sent by the BSL Scripter. all data which is shown by square brackets [] are basically the data sent by the BSL Scripter, and data sent by the curly brackes {} are data sent by the MSP430 target. In your case the {ee} means basically timeout (BSL Scripter doesn't receive any data from MSP430 target).
      I would suggest you to check the BSL Entry sequence on TEST and RST pin. Or use the SLAA535 refered by Mo above, this should work with MSP430F54xx you are using (I have tested it myself).

      Regards,

      Leo Hendrawan

      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • Jens-Michael Gross
      Posted by Jens-Michael Gross
      on Aug 07 2012 08:55 AM
      Guru141810 points

      lhend
      BSL Scripter doesn't receive any data from MSP430 target

      Is it a 5435 or a 5435A? The A types require a specific timing which is almso timpossible to do with an USB->serial converter. THe A types can only be programmed through BSL with a real COM port or the LaunchPad BSL 'interface'.

      _____________________________________
      Before posting bug reports or ask for help, do at least quick scan over this article. It applies to any kind of problem reporting. On any forum. And/or look here.
      If you cannot discuss your problem in the public, feel free to start a private conversation: click on my name and then 'start conversation'. But please do so only if you really cannot do it in a public thread, as I usually read all threads. And I prefer to answer where others can profit from it (or contribute to it) too.

      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • Kailash V
      Posted by Kailash V
      on Aug 07 2012 23:22 PM
      Prodigy170 points

      Thanks Leo,

      I am using 5435(non-A). 

      BTW MSP430f5435(non-A) is a device with dedicated JTAG pins right? So I have to use TST and RST/NMI pins for entering into the BSL. Am I correct? 

      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • Leo Hendrawan
      Posted by Leo Hendrawan
      on Aug 08 2012 02:26 AM
      Mastermind28725 points

      Hi Kailash,

      Kailash V

      BTW MSP430f5435(non-A) is a device with dedicated JTAG pins right? So I have to use TST and RST/NMI pins for entering into the BSL. Am I correct? 

      The MSP430F54xx non-A and A devices are devices with share JTAG pins. The easiest way to make the difference is basically to see whether the device have TEST pin. If it has TEST pin, it is then categorized as devices with shared JTAG pins. However your second argument is correct, for devices with shared JTAG pins, you need to apply the BSL entry sequence at RST and TEST pin, See the following wiki:

      http://processors.wiki.ti.com/index.php/MSP430_FAQ#How_to_invoke_the_BSL.3F

      Regards,

      Leo Hendrawan

      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • Kailash V
      Posted by Kailash V
      on Aug 09 2012 05:56 AM
      Prodigy170 points

      Can someone test MSP430f5435 uart bsl programming? Because I think its not possible to program it through BSL. I somehow managed to enter the BSL by apllying the proper waveforms on tst and rst pin. But when i sent 80h via hyperterminal o any dataframe for the corresponding commands there was no reply from BSL. This was creating a doubt about if the device has entered BSL or not. For this purpose using FET debugger I programmed the chip such that some LEDs will be on all the time. But after I applied the waveforms on rst and tst pins the leds didnot glow. So I inferred that device has enterd BSL. But not responding to the commands. Any guesses what the reason may be? 

      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • Leo Hendrawan
      Posted by Leo Hendrawan
      on Aug 09 2012 06:03 AM
      Mastermind28725 points

      Kailash,

      i tested the BSL on MSP430F5438 (nonA) device before with the SLAA535:

      http://www.ti.com/mcu/docs/litabsmultiplefilelist.tsp?sectionId=96&tabId=1502&literatureNumber=slaa535a&docCategoryId=1&familyId=342

      and it works. This should also apply for the MSP430F5435, since they are more or less the same device (MSP430F5435 is subset from MSP430F5438).

      Kailash V

      But when i sent 80h via hyperterminal o any dataframe for the corresponding commands there was no reply from BSL. 

      Sending a single 0x80 will not give you get a reply from the BSL. The 5xx devices have different BSL protocol. Please refer to the "Flash based BSL" in the SLAU319 documentation. I would suggest you to use the BSL Scripter to check this.

      Regards,

      Leo Hendrawan

      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • Kailash V
      Posted by Kailash V
      on Aug 09 2012 23:27 PM
      Prodigy170 points

      Leo,

      I did not send only 80h but i sent complete data frames for MASS ERASE and some other commands which are not password protected. Also I have gone through the above mentioned file and i found these commands in that file itself. But I have not tested using launchpad. I guess its not 5xx family it comes under 543x_family right? Because thats what I have written in the BSL Scripter command line apllication code.

      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • old_cow_yellow
      Posted by old_cow_yellow
      on Aug 10 2012 00:31 AM
      Guru26595 points

      BSL Scripter may have bugs.

      It may not be able to open COMxx when xx is 10 or higher. You need to go to Windows Hardware Device Manager and change xx to 9 or lower.

      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • Kailash V
      Posted by Kailash V
      on Aug 10 2012 00:33 AM
      Prodigy170 points

      That was when i had connected 2 usb-uarts for some purpose. I had used com14 for communicating with the BSL. But after that i used only one module which was com3.

      I changed the code correspondingly. But still the result is same.

      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    12
    TI E2E™ Community
    • Support Forums
    • Blogs
    • Videos
    • Groups
    • Site Support & Feedback
    • Settings
    TI E2E™ Community Groups
    • TI University Program
    • Make the Switch
    • Microcontroller Projects
    • Motor Drive & Control
    Other Communities
    • Deyisupport
    • Designsomething.org
    • beagleboard.org
    • TI on Element 14
    • TI on TechXchangeSM
    Other Technical & Support Resources
    • WEBENCH® Design Center
    • Product Information Centers
    • Technical Documents
    • TI Design Network
    • TI Technical Articles
    • TI Training

    All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.

    Content on this site may contain or be subject to specific guidelines or limitations on use. All postings and use of the content on this site are subject to the Terms of Use of the site; third parties using this content agree to abide by any limitations or guidelines and to comply with the Terms of Use of this site. TI, its suppliers and providers of content reserve the right to make corrections, deletions, modifications, enhancements, improvements and other changes to the content and materials, its products, programs and services at any time or to move or discontinue any content, products, programs, or services without notice.

    Follow Us Texas Instruments on Facebook Texas Instruments on Twitter Texas Instruments on LinkedIn Texas Instruments on Google+
    TI Worldwide | Contact Us | my.TI Login | Site Map | Corporate Citizenship | mobile m.ti.com (Mobile Version)

    TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs and
    embedded processors, along with software, tools and the industry’s largest sales/support staff.

    © Copyright 1995-2013 Texas Instruments Incorporated. All rights reserved.
    Trademarks | Privacy Policy | Terms of Use