??? 10/16/09 19:00 Modified: 10/16/09 19:00 Read: times |
#169808 - I'm not so sure it's that narrow ... Responding to: ???'s previous message |
Per Westermark said:
Richard Erlacher said:
If it's a hardware problem, it should include a schematic. If that's not there, there's no point in posting it. If it's listed as a firmware problem, it should included a code listing. If it doesn't, there's no point in posting it. But your definition is basically limited to the special case when someone have f..d up. People may have trouble understanding some sections of a datasheet. Then it is impossible to decide if we should consider configuration bits as belonging to firmware, or if the actions these configuration bits performs is part of hardware. Is it? The fair assumption is that one posting a query has (a) thoroughly read and understood the datasheet or made a specific inquiry about a definition, most of which would easily be resolved by a search, and (b) made some preliminary decisions about requirements, available development tools, programming methodology, etc. If someone wants to build a battery charger, they may want a general discussion about how they should supervise dV or dT or how to measure current etc. Is it firmware or hardware? In what way would a battery charger involve an 805x? In what way would an 805x become involved in monitoring dV or dT or measuring current. Isn't that stuff normally done with an oscilloscope?
It can quite often be hard to differentiate the two. The reason why I have been discussing a forum for "general hardware" was just to make some EE people stay on the forum, even if they are considering switching away from 8051 chips. Then they can still discuss the general concept of using an analog output or PWM. Or considerations when using a ground plane. Or what to think about with cabling, transceivers etc if running serial data at Mbit++. If "EE people" are deciding whether to switch away from 805x core chips, they should be visiting the sites that they think will provide them with the information they need. Which 805x-core MCU would you consider capable of "Mbit++" serial communication, aside from the ones specifically intended for Ethernet? Erik Malund seems to have concluded that 805x serial communication tops out at 480-something kbps. That's one thing that's disturbed me about YOUR posts. You seem to think this is a general discussion forum for whatever you happen to want to discuss. For me, if I want to know about ARM or any other non-805x-core MCU, I go to a different site to discuss it. I certainly don't attempt to promote "BIG" processor cores here, nor do I advocate for "small" cores elsewhere. I have advocated for integration of 805x soft-cores with specialized hardware, since programmable logic is a reasonable vehicle vehicle in which to do that, though only when no reasonably priced alternative presents itself. The reason, I feel, that this is a good path is that the 805x instruction set is so well adapted to microcontroller sorts of tasks. As I've often said, microprocessors and microcontrollers were conceived as a replacement for lots of digital logic. The fact that they can behave as computers in the sense that comp-sci students are taught is purely incidental. It's important, but it's nice, though not necessary. That, of course, is not everyone's position, and I recognize that. RE |