Since every device has had a reset sooner or later before you can connect it, I guess it's rather a question of timing, depending on the default settings for MCLK/DCO and the BSL. If you try too soon, you'll fail, if you try too late, you'll be after the BSL code and maybe in the middle of nowhere (empty flash) or in or even after the startup code. Some devices have a tight schedule for the BSL startup sequence (e.g. the 54xxA) or start with a fast clock (whole 5x series starts in th e16Mhz range) while others are rather relaxed or even slow (the 1x series with its ~600kHz clock).
Unfortunately, when using the TI library, one has no influence over the connect/timepout cycle, and since the device is unknown before the connect (well, one could tell by forcing a certain MCU type), I guess there's ony the way to try and retry. JMGross ----- Ursprüngliche Nachricht ----- Von: Daniel Beer Gesendet am: 25 Okt 2010 22:52:24 > The identify command failing is probably related to the commit you did > last week, I suppose? > > > fet: retry with reset on connect if the first attempt fails. Yep, that's it. Some devices require a reset on startup, and some fail to connect if you do it. So I ended up sort of brute forcing it -- it now just tries first without the reset and then again with a reset if that doesn't work. Cheers, Daniel ------------------------------------------------------------------------------ Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev _______________________________________________ Mspgcc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mspgcc-users
