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

C164 OTPprogrammind failed

Hello!
Could somebody help me (again)?
I programmed a C164 BC-Step with the MEMtool.
Something was programmed,but verifying shows a lot of differences (about 800).I looked at the programmed data:there are some parts wich are correct,but are programmed about 20hex behind the address it should...
Please answer me if somebody knows something about this!?
Thanks a lot hannes

Parents
  • Hello again!
    I'm used to work with the monitor-configation
    called 'Phytec KC-164CI' (the name of my board).Following your hints I set ROMS=1 and Romen=1 too in the startup file but I don't know if you did mean it-or have I to use 'Monitor 166 in ROM' option?(I've never used befor).
    I don't really understand how I could read the contents of OTP in monitor mode?
    Have a nice day
    best greetings hannes

Reply
  • Hello again!
    I'm used to work with the monitor-configation
    called 'Phytec KC-164CI' (the name of my board).Following your hints I set ROMS=1 and Romen=1 too in the startup file but I don't know if you did mean it-or have I to use 'Monitor 166 in ROM' option?(I've never used befor).
    I don't really understand how I could read the contents of OTP in monitor mode?
    Have a nice day
    best greetings hannes

Children
  • Hello Hannes,
    you have to recompile your Mon166 with the modifications I suggested and reprogram it into the flash of your EVA board.
    Then, in the 164 memory space you will see the internal rom, which is not disabled at startup; using the uV2 debugger and simply displaying a memory area (from 0x10000) you will see the internal ROM listed.
    Look at the 164 user's manual to understand what the ROMEN=1 and ROMS1=1 settings do.
    If you want to do some experiment, you can even use the Infineon Minimon to read and list the 164 internal ROM.
    Ciao
    Bruno