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

Good substitute for obsolete Philips 89C51RD2 ???

Hello, in an ironic twist, the Philips 89C51RD2 we use for the control panels on Philips CT scanners has been discontinued due to Philips selling it's semi-conductor operations last year. So I was wondering if anyone had a good substitute they had tried ???

Thanks,
Don

Parents
  • Hello again, the 89V51RD2 appears to be absolutely
    NOT fully SW compatible with the 89C51RD2.

    Besides any HW differences, anyone using
    In-Application-Programming (IAP) or has their own
    downloader for In-System-Programming (ISP), there
    are differences that can only be resolved by changing
    and recompiling both the 8051 IAP code & the external
    ISP downloader code. This would seem to really throw
    a wrench into the works for anyone without SW support.

    In our 8051 application we have an option to
    change some settings which must be remembered between
    resets. We store them in an ascending list in unused
    flash, starting at 0xC000 by enabling the boot-rom
    code & calling the flash byte program function. They
    changed the register & bit to enable the boot-rom code
    from AUXR1.5 (enboot) to FCF.0 (BSEL) They also changed
    the address of the IAP entry address from 0xFF00 to 0x1F00.

    We also have our own ISP downloader in an
    external device which will have to change since the
    Specify Oscillator Frequency function is no longer
    supported. If you have an external downloader which
    waits for the returned "." as an acknowledge to that
    command, it will wait forever, since the SOF is ignored.

    I'd really like to know why these changes were
    made since they don't really appear to enhance the
    functionality of the device any. In addition, there
    may be other changes that I'm not yet aware of.

    Technical Note TN06007 - V51RX2 Migration

    www.semiconductors.philips.com/.../TN06007_V51RX2_Migration.pdf

    Thanks,
    Don

Reply
  • Hello again, the 89V51RD2 appears to be absolutely
    NOT fully SW compatible with the 89C51RD2.

    Besides any HW differences, anyone using
    In-Application-Programming (IAP) or has their own
    downloader for In-System-Programming (ISP), there
    are differences that can only be resolved by changing
    and recompiling both the 8051 IAP code & the external
    ISP downloader code. This would seem to really throw
    a wrench into the works for anyone without SW support.

    In our 8051 application we have an option to
    change some settings which must be remembered between
    resets. We store them in an ascending list in unused
    flash, starting at 0xC000 by enabling the boot-rom
    code & calling the flash byte program function. They
    changed the register & bit to enable the boot-rom code
    from AUXR1.5 (enboot) to FCF.0 (BSEL) They also changed
    the address of the IAP entry address from 0xFF00 to 0x1F00.

    We also have our own ISP downloader in an
    external device which will have to change since the
    Specify Oscillator Frequency function is no longer
    supported. If you have an external downloader which
    waits for the returned "." as an acknowledge to that
    command, it will wait forever, since the SOF is ignored.

    I'd really like to know why these changes were
    made since they don't really appear to enhance the
    functionality of the device any. In addition, there
    may be other changes that I'm not yet aware of.

    Technical Note TN06007 - V51RX2 Migration

    www.semiconductors.philips.com/.../TN06007_V51RX2_Migration.pdf

    Thanks,
    Don

Children