Two Phase Waveform #341
Replies: 8 comments 10 replies
-
Huh the DB28 does come in dip. I always wondered why the heck anyone would use DB28s (other than the chip shortage) - in tssop they take up about the same board area as the 32's are somewhat gimped, and are more annoying to solder than the 0.8 pitch TQFP. Makes sense if it caters to the DIP crowd. Personally when I want a DIP-like mcu (rare, I hate solder less breadboards) I just mount a 32 on a breakout and solder on 2 0.1 headers. |
Beta Was this translation helpful? Give feedback.
-
Aw gee @mosqu-ito - you didn't have to go to all this effort! Say, what do you have in mind for this Swiss army knife? Just out learning? |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Three, just so I can have one more than you. They just go wherever they look nice, right? ;) |
Beta Was this translation helpful? Give feedback.
-
I won't make this a new thread under Q&A because I know others have had this kind of issue before; but when I went to program this, it complained that the Device ID was 1E9535 when it was expecting 1E9532. Naturally I just went into AVR32DB48.py and changed it. So far so good. For what it's worth, the chip came from Digikey. |
Beta Was this translation helpful? Give feedback.
-
You did not do the correct thing. The correct thing to do was a two step process:
There sounds like there is not anything here to discuss, other than "How the fuck did you screw THAT up man? Don't you test your code?" (to which the answer is "no, of course not, I'm engineering, not quality assurance". I'll note that while Microchip swore up and down that we'd never have problems with stuff derived from pymcuprog working with new products because they'd keep everything up to date, I added those files myself, like 6 months after Microchip started shipping them and still hadn't updated it, and besides, the code as supplied was so dog slow as to be useless anyway, and after I made it perform acceptably, it was so far diverged from their tree that I couldn't merge in changes anyway. So this is very much an issue, not a discussion. The only "discussion" that would be relevant would be insults directed at me. Which are of course always welcome - I used to play an MMO, at the top tiers of the game, so you have to really really work to make an insult that produces a response other than "That's a fair characterization, yes" or laughter We are actually changing the name of the library so that pathological library updaters (the people who, without actually having done so themselves such that they'd know it wouldn't result in anything resembling functionality), instruct people on the forums to delete the pymcuprog directory we supply and install that basketcase from from microchip through pip) will be dissuaded from updating it and then bitching about all the problems they encounter Discussions I have one chance to notice as they go past my email box, which sometimes receives so many emails in a day (most worthless) that it can go to over one page). The github issues section is my to-do list. |
Beta Was this translation helpful? Give feedback.
-
Finally, now that we're on a 48 pin DB, we have, not two, but three op amps. UnityGainFollower(HALF_VDD, 2); // Input, Amp#, ToPin (default true) GREEN Because the DBs bring us Op Amps, Microchip provides us with a voltage reference |
Beta Was this translation helpful? Give feedback.
-
Two-phase waveforms are super useful when it comes to precise motion control, but what really takes it to the next level is combining them with sound dampening rollers. They keep everything running smoothly while cutting down on noise—perfect for keeping things efficient and quiet at the same time! |
Beta Was this translation helpful? Give feedback.
-
I've included fully five decoupling capacitors for the sole purpose of galling @Warren52
Beta Was this translation helpful? Give feedback.
All reactions