This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Dallas 390 Evaluation

Several years ago we started a project using the Dallas 390 but we run into problems, at that time we did not know if they were bugs in the micro it self, board design or faulty assemply.

We want to retake the chip and am looking for some feed back regarding the performance of the microprocessor and if there is any unresolve bug issues.

Thanks

Parents
  • This not really the ideal place to ask this question.

    That said, I've been programming the '390 for quite a while, so maybe I can provide some insight. Older revisions had a considerable number of rather serious issues --- viz the errata sheets. You really want to go over those carefully to make sure none of those catch you off-guard. The current revision, C3, has all of those fixed. They did fix some of the issues by removing functionality (e.g. one CAN power-save mode is gone), some by changing the specification of some features (e.g. one of the baud rate generator modes in C3), others by simply fixing the silicon.

    I had the opportunity of discovering one new erratum myself, and found Dallas quite helpful. They really did go out of their way to suggest workarounds, and they did update the errata sheet in a timely fashion, and they fixed the known bugs in the next revision. What more could be asked of them?

Reply
  • This not really the ideal place to ask this question.

    That said, I've been programming the '390 for quite a while, so maybe I can provide some insight. Older revisions had a considerable number of rather serious issues --- viz the errata sheets. You really want to go over those carefully to make sure none of those catch you off-guard. The current revision, C3, has all of those fixed. They did fix some of the issues by removing functionality (e.g. one CAN power-save mode is gone), some by changing the specification of some features (e.g. one of the baud rate generator modes in C3), others by simply fixing the silicon.

    I had the opportunity of discovering one new erratum myself, and found Dallas quite helpful. They really did go out of their way to suggest workarounds, and they did update the errata sheet in a timely fashion, and they fixed the known bugs in the next revision. What more could be asked of them?

Children
No data