Started by TomP, June 26, 2007, 09:03:58 AM
Quote from: TomP on July 17, 2007, 10:57:49 AMWell it looks like we're not out of the woods yet. This latest build had 19 systems that wouldn't program. Out of those 19, I was able to program 5. Some were RB2HBA and some were RB2BA. Dropped the baud down to 19.2k (accidentally did one at 7200! Sheesh, what a long time that took!)
Quote from: TomP on July 17, 2007, 10:57:49 AMMy scope says that the ones that don't program aren't replying to the first "U" that FM sends.
Quote from: TomP on July 17, 2007, 10:57:49 AMIt's interesting that my PC seems to be able to program more boards than the laptops & PC's used in the production area. Could that mean that those RS232 level shifters are adding skew to the characters to where the RB2's don't recognize them?
Quote from: Jan Waclawek on July 18, 2007, 12:53:59 AMIf you follow Andy's recommendation, autobauding at a LOW baudrate (don't be shy to go as low as 2400) then switching to higher baudrate using the dedicated ISP command, you will gain both reliability in autobauding and high programming speed.
Quote from: Jan Waclawek on July 18, 2007, 12:53:59 AMDo you mean, they don't reply anything, or they reply garbage?In the first case, you might have the infamous "bootvector loss" problem... What sort of reset circuit do you use?
Quote from: Jan Waclawek on July 18, 2007, 12:53:59 AMYes. If you have a look at the excell sheet on my webpage I mentioned above, you can play with the value of skew/assymmetry and see how it influences the probability of correct autobaud at various baudrates.Actually, once you have connected your scope, did you measure the skew/assymmetry, as present on the '51Rx2's RxD pin?
Quote from: TomP on July 19, 2007, 12:20:53 PMIn the Advanced Options/Communications tab of FM, what effect do the 6 Clock/12 Clock settings have?
Quote from: TomPNo reply at all. Not even garbage.Using a MAX810 for reset.