dronus 0 Posted June 8, 2016 Share Posted June 8, 2016 I am using energia on Linux with several different LaunchPad models. For most of them, Energia forces an update of the FET programmer firmware. If started by the corresponding menu option, the update will take place to some high percentage but then fail, leaving the board in a bricked state. This happens for almost any LaunchPad that needed the update. I think Energia should be more cautionous, maybe exit the update if something would'nt work out, but don't brick boards in general. Quote Link to post Share on other sites
dronus 0 Posted June 8, 2016 Author Share Posted June 8, 2016 The recovery as described in http://www.aglaglobal.com/content/recover-broken-fet-msp430f5529-launchpad-after-ccs-crashes-during-firmware-update works, as does the update by command line. So I guess it is an Energia problem. Quote Link to post Share on other sites
spirilis 1,265 Posted June 8, 2016 Share Posted June 8, 2016 There's a bunch of /etc/udev.d/rules entries you should have that might "grease the skids" for Energia FET updates. Unfortunately I don't have them handy anymore (blew away my Linux install and went with a new Windows 10 laptop...) edit: Are you using Energia as a normal user or as root? This is important, what those "udev rules" I mentioned do is allow normal users (or users in the "dialout" group usually) to have write access to the USB VID/PID of the FET's USB bootstrap loader. Quote Link to post Share on other sites
LiviuM 43 Posted June 8, 2016 Share Posted June 8, 2016 Hi spirilis,in the attachment are the rules I'm using with my OpenSuse (Leap).I think tivac rules are twice, not sure which one is the good one, maybe you can find the right one.I'm using a tivac TM4C129 and a 430G1 Launchpads as normal user (member of dialout group).Hope it helps a little,Liviu energiaUdevRules.zip Quote Link to post Share on other sites
energia 484 Posted June 13, 2016 Share Posted June 13, 2016 I have never seen a brick happen. It is indeed possible that sometimes the update fails but should always be recoverable by selection "Tools->Update Programmer" again. It can sometimes take multiple tries to finish the upgrade successful. Quote Link to post Share on other sites
energia 484 Posted June 13, 2016 Share Posted June 13, 2016 P.S. the next release will no longer use mspdebug but instead use DSLite that comes from TI directly. This tools is a lot more stable and I have never seen it failing an upgrade. Quote Link to post Share on other sites
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.