• State TI Thinks Resolved
  • Locked Locked
  • Replies 18 replies
  • Answers 4 answers
  • Subscribers 79 subscribers
  • Views 3109 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Deboxing the DAC161S055EVM

Michael Choi
Expert 1345 points
Other Parts Discussed in Thread: DAC161S055EVM, DAC161S055, MSP430-FLASHER, UNIFLASH, MSP430F5529

Dear Sir:

     I purchased the DAC161S055EVM booster board that connects to the USB MSP430F55529 Launchpad.

     I am in the process of "deboxing" the kit and I am running into difficulties installing the software for this kit.  

     For your convenience I have enclosed a link to the webpage:

      http://www.ti.com/tool/dac161s055evm         

      Let us make the Boost Kit user's guide a reference that we may both rely upon:

      http://www.ti.com/lit/ug/snau171/snau171.pdf   

      When I get to this point in the user's guide:

2.2.1 MSP430 Firmware Upgrade Application Installation

       The software does not install correctly:

        Below is a snapshot of the error message that I receive:

    

      No matter what format I save the file in, I get the same error message that you see above.

      Can anyone tell me a solution to this problem?

  • 0
    Expert 1345 points
    By the way, the operating system that I am using is Windows 7 Professional 32 bit.
  • 0 in reply to Michael Choi
    Expert 1345 points

    Also, please take notice that I have changed the name of the download example to *.exe and I still get the same error message.  

    My apologies, for not mentioning this when I first started this post.

  • 0 in reply to Michael Choi
    Expert 1345 points
    I have inserted a snapshot of what I see on my computer screen for your convenience.
  • 0 in reply to Michael Choi
    Expert 1345 points
    I should have explicitly wrote that I changed the filename extension to *.exe, however, I received the same error message. I will try to insert a snapshot of what I see on my computer below:
  • 0 in reply to Michael Choi
    TI__Guru 68116 points
    Hi Michael,

    Sorry for the long delay. I used Internet Explorer 11 to download the same firmware upgrader software and also saw that it left off the .exe when it downloaded (I am reporting this issue, but unfortunately is something I've seen across a few different websites when using IE). But if I add the .exe to the end of the file manually, I am able to run it just fine (though I do have a 64-bit system). I also found that if I used Chrome as my browser to download the file instead, it does correctly download with the .exe.

    Can you please try to use another browser (Chrome or Firefox) to download the file again and see if this resolves your issue? I will also try to see if we have any 32-bit machine here to confirm that it works ok.

    -Katie
  • 0 in reply to Katie Pier
    TI__Guru 68116 points
    Hi Michael,

    We also tried a 32-bit machine here but it worked correctly. I was told that there are a lot of articles on the web about this specific error though (it's not unique to MSP but is a windows thing) that might help you figure out if there is a setting in your system that you need to change or something.

    Regards,
    Katie
  • 0 in reply to Katie Pier
    Expert 1345 points

    Dear Katie;

         I realized that you replied to my post before the moderator posted my last post.  

         The TI web moderator controls when - the time - when posts are inserted.    Therefore, you don't see all of my posts in a timely manner, nor do you see all the snapshots I had posted (I believe a snapshot I uploaded was omitted).      The use of a forum moderator can disrupt efficient communication.  

         When you wrote:

    "But if I add the .exe to the end of the file manually, I am able to run it just fine (though I do have a 64-bit system)."

         I realized that you were not able to read my posts that were made in process.   I tried to re-name the file with an *.exe extension, however, the program did not run.  

         I believe that you can help me and help yourself - to get this post off your "things to do list" by corresponding with a TI engineer who works with component.     I think that TI can satisfy the inconvenienced  customer (me) better by sending me a simple program written in assembler or C (in traditional format - the straightforward way of programming that we all had to learn college or high school) that gets the DAC to work,   Since the hardware platform is already set up and a TI engineer had to have already made a simple program for this kit, solving this problem is nothing more than few simple button clicks on an email browser. 

       I can see already that getting this GUI up and running is going to become a long and drawn out - time consuming - and convoluted process.   This is going to become a miserable experience for all parties to this matter.  

       However, all this can avoided by sending me, or posting, a simple program written in traditional format, that works on the launchpad.   Hopefully, you will see "utility" of my suggestion because it benefits all parties to this matter.     Please send, or post, a simple program, and I will be a satisfied TI customer.

        Thank you for your replies - your consideration was appreciated.   

  • 0 in reply to Michael Choi
    Expert 1345 points
    Dear Katie;

    I forgot to add that I tried Mozilla Firefox and the program itself was not visible on my computer screen.

    Please take my suggestion under consideration. Thank you.
  • 0 in reply to Michael Choi
    TI__Guru 68116 points

    Hi Michael,

    I saw that you tried adding the .exe but we were unable to reproduce your issue here, even on a 32-bit windows system, so it is hard to say what your problem is other than the error message you saw is a windows error message that is fairly generic and we unfortunately can't give much more guidance since we don't have your exact PC to test on and are unable to reproduce on our 32-bit windows system here.

    For getting your DAC firmware that is provided with the board to be loaded, you should be able to use something besides just the USB firmware upgrade example that is mentioned in that boosterpack user's guide. Here are two alternative options for loading the provided dac161s055_fw-v0.89.txt file that comes with the DAC boosterpack:

    Option 1: Use the Python USB firmware upgrader. software-dl.ti.com/.../Python_Firmware_Upgrader-5_00_01.zip
    -Unzip this file, then run Python_Firmware_UpgraderGUI.exe.
    -Hold down the BSL button on the MSP430 F5529 Launchpad while plugging it into the PC with the USB cable, then release the button. The Python GUI should have a message that it has detected the device.
    -Go to File > Open User Firmware... then navigate to the file that you want to load, in this case the dac161s055_fw-v0.89.txt file that came with your DAC device and is mentioned in the boosterpack user's guide.
    The code should get loaded into the device.

    Option 2: Use MSP430-Flasher www.ti.com/.../msp430-flasher
    -Install the MSP430-Flasher software on your PC
    -Modify the example .bat file to have your dac161s055_fw-v0.89.txt be what is loaded. You may need to move it into the same directory or specify the path to the file.
    -Alternately, from the command line, navigate to the install location C:\ti\MSP430Flasher_1.3.7 and run MSP430Flasher.exe from the command line. To get a list of what parameters to use, try running it as MSP430Flasher.exe -h and it will have an explanation of all of the options.

    Option 3: Use CCS Uniflash: www.ti.com/.../uniflash

    Option 4: Use Elprotronic Fet-Pro430 Lite software: www.elprotronic.com/productdata

    For more help specifically with the DAC161S055EVM boosterpack rather than just getting the MSP to load with code, you may need help from the Data converters forum because I really only support MSP430 and MSP432, without knowing anything about this DAC (that forum should have people more familiar with this kit). But hopefully the information I've provided above will at least get your code loaded.

    Regards,
    Katie

  • 0 in reply to Katie Pier
    Expert 1345 points

    Dear Katie:

          I do not believe that this file came with my device:

    dac161s055_fw-v0.89.txt

          Please send me or directly link me to this file.  

          Also, can you contact a TI engineer and send me code to work with my EVM directly that is written in traditional format?   This would simplify matters and be greatly appreciated.

          Thank you.

  • 0 in reply to Michael Choi
    TI__Guru 68116 points
    Hi Michael,

    That file was simply referred to in the user's guide that you linked in your original post, so I thought you had it already - sorry for the confusion. I think for more information about the EVM software and how it works, you will need to post in the Data converters forum because that will put you in contact with the team that wrote/owns that software - unfortunately I've never used it before because it was not written by MSP but rather by the team that works on the DAC on the boosterpack. I was just trying to help you get the code loaded since you were having issues with the tool that the boosterpack user's guide told you to use, and that tool is something from my MSP team.

    I looked on the tools page for the DAC161S055EVM that you linked on your first post: www.ti.com/.../dac161s055evm If you scroll down that page to where it says "Software", you can find a link to download the software that the user guide refers to (DAC161S055 EVM GUI(Rev. A)): www.ti.com/.../snoc021
    Extract this zip file, and unzip DAC161S055_Installer.zip and then run the installer. After it installs, you can find the file at C:\Program Files (x86)\Texas Instruments\DAC161S055\Firmware\dac12xSxxx_fw-v0.87.txt. I think that is a binary image of the demo firmware and is what the user's guide was telling you to load. There is also a zip file included in the same Firmware folder that contains the source code for the same program I believe. But if you have more questions about this source code/firmware, you're going to have to ask in the Data converters forum I think because I don't know anything about this firmware for controlling the DAC.

    Regards,
    Katie
  • 0 in reply to Katie Pier
    Expert 1345 points
    Dear Katie;

    I tried option 1 and 2. Option 2 resulted in an error that is not convenient to fix at this time. I will elaborate upon this error in future messages if necessary. I am focusing upon option 1 because I believe that a quick solution may exist:

    I am new to the Python Firmware Upgrader software. I am not certain if I was successful in putting the MSP430F in bootstrap loader mode correctly. However, whether I did or not put the MSP430F in bootstrap loader mode, I know that an error condition exists.

    Please interpret the following error messages that I have received.

    Screenshots of the error messages are provided either below this message or in the following posts (there is problem with this website menu options - with regard to inserting files). Please take notice that the MSP430F launchpad was configured in the "new in the box" state before the Python program was utilized (this information will serve as a reference point for you).
  • 0 in reply to Michael Choi
    Expert 1345 points

    Dear Katie;

    I managed to get a hold of the dac161s055_fw-v0.89.txt file that you were referring to.

    I tried options 1 and 2. Both failed.

    Option 2 turned out to be a complete disaster. For some unknown reason, the software appeared to operate on the msp430f once (but the download failed) and then whenever I try to click on the program, the MSP430 Flasher shuts itself down. Worse yet, I can't uninstall the program. Programmatically, somehow, the uninstall path to enable the uninstall program located in the Windows taskbar was either disabled or erased. When I click on the uninstall icon, Windows keeps searching for the shortcut address. There is no listing of the program when I utilize the control panel uninstall option.

    There may be hope with my attempt to utilize option 2, the Python USB firmware upgrader. I am not certain if I was able to put the msp430f in boot loader mode. You will have to interpret some screenshots to determine if this task had been accomplished or not.

    There is a problem. I am trying to upload the screenshots but the option to upload the files - menu choice - is not present. I am going to work on sending you some screenshots. Before I upload the screenshots, I want you to know that the MSP430F is pre-configured in the "new in the box" msp430f launchpad software program. This will be a reference for you if you attempt to experimentally see where the source of the program is originating from.

    I will try to email you the screen shots if I can't upload them.

    Thank you for your efforts.

  • 0 in reply to Michael Choi
    Expert 1345 points
    Dear Katie;

    I managed to upload the screenshots.

    Can you show me a screenshot of what I should see when the MSP430 bootloader has made proper connectivity using the Python Firmware Upgrader?

    I would like to verify if the second screenshot showing the rocket necessarily implies that I got the boot loader in its proper state (or is the screenshot of the rocket only implying that a text editor function is working but not the boot loader function).
  • 0 in reply to Michael Choi
    TI__Guru 68116 points

    Hi Michael,

    Thanks for the information and the images. From my testing, I can see the same messages as you if I do not have the device in BSL mode (except for the rocket image - I'm actually not sure how you got that to show up).

    Here is some comparison:

    If I am not already in BSL mode when I start the GUI, I see this:

    If I then unplug the board, hold down the button on the Launchpad marked "BSL", insert USB, and release the button the Launchpad marked "BSL", my part should now be in BSL mode. After doing this, do File > Rescan HID bus in the GUI. You should see this if it finds the board in BSL mode:

    At this point, you now can successfully select and load code without error.

    As for the other image you saw (with the Tkinter callback exception message), I only see this error if I have my device NOT in BSL mode (did not say ready...) and try to select a file to load anyway. You'll get that error because the part wasn't in BSL mode yet.

    Regards,

    Katie

  • 0 in reply to Katie Pier
    Expert 1345 points

    Dear Katie;

          I would like to thank you for your rapid and informative replies.   You are really on the ball.   I wish you wrote the booster pack user's guide.

          There was a miscommunication between us that you may not be aware of.   When you wrote your post in early December about how to locate the binary file (*.txt), I just saw that post TODAY.   I don't know why that post was not visible to me until today.    I really don't like a moderator viewing our posts before we can post to the website because he makes the decision to post our replies or not.     Not only is there a time delay for us to obtain information from each other but also our communications can appear garbled if the moderator decides when to post our replies.     You could have been blaming me for not finding the *.txt file but I never saw your post until today.   I managed to get a hold of the binary *.txt file from another TI engineer at another forum.    I wish you wrote the booster pack user's guide, you make everything so easy to understand.  

          I am going to try again with this booster pack and see if I can get it working. 

          I would like to ask you one question before I sign off.   This is the question:

          The user goes through a lot of trouble to use the BSL and to flash the MSP430F.   It would appear to be much simpler to write a program in the CCS IDE and have the user work the program in the CCS environment (after all it is a much more reliable means of processing information).    What was the advantage of deploying the EVM software using a BSL followed by a series of upgrade installations?   What was the advantage for each step?

          The complexities involved in this whole matter has made me a little curious.   I would like to know why this means was chosen?

           Thank you again for your most excellent technical support.   Hopefully, this reply will be posted in a timely manner.    

  • 0 in reply to Michael Choi
    Expert 1345 points
    Dear Katie;

    I wanted to answer your question when you wrote:
    "
    Thanks for the information and the images. From my testing, I can see the same messages as you if I do not have the device in BSL mode (except for the rocket image - I'm actually not sure how you got that to show up)."

    When you wrote:

    " (except for the rocket image - I'm actually not sure how you got that to show up)."

    When you get the MSP430F5529 USB Launchpad in the mail, there are a couple of programs already installed in the Launchpad right out of the box. When I got my USB Launchpad, the instructions were to open any text editor (have blinking cursor operating within the text editor) and then to press a pushbutton. When you pressed the pushbutton, the MSP430F would then demonstrate USB connectivity by sending that rocket image to the text editor via the USB cable.

    Have a great night and, again thank you for your great technical support.
  • 0 in reply to Michael Choi
    TI__Guru 68116 points

    Hi Michael,

    For your issues with E2E: I'm sorry to hear of it. I've not heard of this moderation issue before, so I'm going to make sure to forward your feedback to our E2E team here to see if they can figure out what problem you are experiencing. I'm not sure if they'll need more information from you about what happened to figure it out or not. But my understanding is that when I post it shouldn't be going through any moderation (I have moderator rights myself actually) so I'm not sure why my post may not have appeared for you at first. Maybe there was something else going on.

    Michael Choi said:

    I would like to ask you one question before I sign off.   This is the question:

          The user goes through a lot of trouble to use the BSL and to flash the MSP430F.   It would appear to be much simpler to write a program in the CCS IDE and have the user work the program in the CCS environment (after all it is a much more reliable means of processing information).    What was the advantage of deploying the EVM software using a BSL followed by a series of upgrade installations?   What was the advantage for each step?

          The complexities involved in this whole matter has made me a little curious.   I would like to know why this means was chosen?

    The MSP team does not actually own support for this DAC161S055EVM nor was it designed by us - the EVM was made by one of the TI analog teams and just happens to use an MSP as the micro on the board. So I could help for your case because I do know about the MSP430 BSL and our tools, but unfortunately I don't really have any answers about why different design decisions were made for the EVM. For questions and feedback (which I think is some good feedback) I would recommend posting these concerns in the Precision Data Converters forum - I think you'll be more likely to get in touch with the right team there.

    FYI I'll be out of office for the holidays after today, so I may not respond if you post in the next week or so. Happy Holidays and Happy New Year!

    Regards,

    Katie

**Attention** This is a public forum