| ??? 07/16/09 15:23 Read: times |
#167424 - it's all about the timing ... and the support Responding to: ???'s previous message |
Erik Malund said:
SiLabs parts ... I'm not sure why, since they [not] capable of providing ... the necessayr number of I/O's.
SILabs have many 8-porters, which, even if 64 I/Os are not enough, gives a lot of flexibility. If it's not enough, it's not enough, regardless of how much flexibility it offers. after communicating at with their support staff .... I had to give up on 'em.
If I were to choose a chip based on the quality of 'examples' and or the quality of the support staff, I would still be looking for chips instead of making product. Well, when they tell you that if you don't use this programming language, they won't support you, then they're off my list. wading through their endless examples of 'C' code with little information about precise timing, and careful synchronization of events
I know that you live in the past, today most code in C and, if you can not figure out to code in assembler (why you want that I can not figure out) based on an 'example' in C you are even more a luddite than I thought. I did not know you needed 'examples' The 300+ page datasheets DO give "precise timing", if you can not figure out the cache lock, that is not their fault. I can "wade through the endless examples of code with little information about precise timing, and careful synchronization of events" at the website for your beloved Dallas or any other manufacturer. you have decided (as so often before) that if some company will not do it your way it is no good. Erik I'd think you'd find that quite self-explanatory. While the datasheet provides plenty of information, it says nothing about the timing of the 'C' code. The 'C' code tells you nothing about the timing, too. In addition, of course, the support folks would ordinarily be able to tell you how long something takes. When it's in 'C' ... well ... they can't do that, can they? RE |
