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
Parents
  • step1: Read "K. Ayala" - to understand architecture
    step2: Read "Mazidi" - to understand programming 8051 in asm & C

    Mazidi is a good book. You can find it in the local book store.
    But dont be totally dependent on it as there are few (not so bothering to a newbie) mistakes in the book. You may realize those mistakes once you have gained some expertize in 8051.

Reply
  • step1: Read "K. Ayala" - to understand architecture
    step2: Read "Mazidi" - to understand programming 8051 in asm & C

    Mazidi is a good book. You can find it in the local book store.
    But dont be totally dependent on it as there are few (not so bothering to a newbie) mistakes in the book. You may realize those mistakes once you have gained some expertize in 8051.

Children
  • Mazidi is a good book. You can find it in the local book store.
    But dont be totally dependent on it as there are few (not so bothering to a newbie) mistakes in the book.

    If you use, virtually, any processor still made Mazdi has no info on the plethora of improvements to the I/O of modern '51s.

    I recall some Mazdi believer who wanted to bit-bang I²C using a processor that had it in hardware.

  • Is that some plural for Mazda?

    I suspect the real problem is the lack of any competence in those teaching from the books, instead of having any real world, or current, experience.

  • I recall some Mazdi believer who wanted to bit-bang I²C using a processor that had it in hardware.

    It was not me who said that, but I have done it.

    Why? What a terrible thing to do you probably shout.

    Unfortunately, some I²C hardware implementations are not as good as they should be. So doing it the hard way is sometimes the only sensible way out of a tricky situation.