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.

CCS/MSP430G2553: Uniflash v5.3.1 error 'Cannot read property 'DS' of undefined'

Part Number: MSP430G2553
Other Parts Discussed in Thread: UNIFLASH, MSP-FET

Tool/software: Code Composer Studio

Hello,

Yeah, sorry, yet another one of these.  :)

Our factory is having trouble programming with Uniflash v5.3.1 on Win10.  I am preparing a list of things to troubleshoot, including the items mentioned in many helpful posts in the forum about this error (Admin, anti-virus, disable wifi, re-install, etc.).

I have one question regarding one of the items.

e2e.ti.com/.../819208

Ki's last post mentioned this:

> It is not a driver issue. It looks like a reliability issue. Can you have the customer try lowering the TCLK setting in the ccxml file?

http://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_xds110.html#jtag-clock-speed-considerations

In the context of MSP430G22553, with programming via SBW, where is the clock setting (xml) for slowing the programming clock?  I haven't found one yet.

A slower clock may not be needed, but the jig's original SBW cable was poorly implemented and twisting the cables together improved things.  Later, the CM then changed the cable to shielded (not sure how well implemented) and detection appears to be broken most or all of the time.

Any input would be welcomed!

Many thanks in advance!

Kind Regards,

David McRell

  • Hi David,

    Can you generate and attach both GUI and DS logs like in the thread that you referenced?

    David McRell said:
    In the context of MSP430G22553, with programming via SBW, where is the clock setting (xml) for slowing the programming clock?  I haven't found one yet.

    The TCLK comment in the other post would apply to our XDS debug probes and not the MSP-FET.

    ki

  • Hello Ki,

    Thank you for your reply.

    I will request log.  Probably won't be ready until Monday.

    > The TCLK comment in the other post would apply to our XDS debug probes and not the MSP-FET.

    Ok. Is there is no way to decrease SBW clock?  If it helps any, I failed to mention in original post that we are using Launch Pad MSP-EXP430G2 v1.5 with UniFlash.

    Thank you!

    David McRell

  • David McRell said:
    Ok. Is there is no way to decrease SBW clock? 

    You can try playing with the below setting in the ccxml file:

    Any luck with the log?

    Thanks

    ki

  • Hello Ki,

    Thank you for the speed tip.  I had noticed this in CCS but was not sure if it mattered or how to implement it.  It appears to default to Medium, so I will try Slow.

    I am still waiting for log files.  Perhaps within 1 day.

    Thanks!

    David

  • ello Ki,

    1. There is strong evidence that the production jig has some poor pogo pins, causing intermittent connection to our PCBAs. IOW, hardware issue.

    2. Just in case, attached are log files.

    Thanks for your help!

    0285.ds.log

  • I cannot Reply with the xml file attached (An error occurred. Please try again or contact your administrator).  I've renamed it to .txt.

    <?xml version="1.0" encoding="UTF-8" standalone="no"?>
    <configurations XML_version="1.2" id="configurations_0">
    <configuration XML_version="1.2" id="configuration_0">
            <instance XML_version="1.2" desc="TI MSP430 USB1" href="connections/TIMSP430-USB.xml" id="TI MSP430 USB1" xml="TIMSP430-USB.xml" xmlpath="connections"/>
            <connection XML_version="1.2" id="TI MSP430 USB1">
            	
            		   <instance XML_version="1.2" href="drivers/msp430_emu.xml" id="drivers" xml="msp430_emu.xml" xmlpath="drivers"/>
            	
                
                <platform XML_version="1.2" id="platform_0">
                    <instance XML_version="1.2" desc="MSP430G2553" href="devices/MSP430G2553.xml" id="MSP430G2553" xml="MSP430G2553.xml" xmlpath="devices"/>
                </platform>
            </connection>
        </configuration>
    </configurations>

  • Thanks. I have sent the log to the engineering team for further analysis. I will pass on any updates I receive.

    Thanks

    ki

  • Based in the logs, it looks like the program was loaded correctly despite the cryptic DS error message. Can you confirm that the load was successful on your end?

    -As for the error message itself, does it happen frequently (every time)?

    -Have you tried running the UniFlash CLI (as mentioned in the thread you first referenced)?

    Also, could your try updating to the latest UniFlash version to see if that helps at all? 

    Thanks

    ki

  • Hello Ki,

    Sorry for my delayed reply.  I just returned from vacation.

    Thank you and the engineering team for your help with the logs.  I'm glad there are no warning flags in the logs.

    Therefore, it is very likely that at the outset that the jig had intermittent connections, plus there was learning curve issues.  The error message appears to now be non-existent or too infrequent to matter in light of the aforementioned intermittent connections.  With understandable travel bans, such troubleshooting is difficult to rapidly ascertain.  At this time, I believe this thread should be closed.

    I do plan to switch to CLI eventually, as such is already used for a different task.  But this is for later.

    > Also, could your try updating to the latest UniFlash version to see if that helps at all?

    I definitely will consider this.

    Many thanks!

    David McRell