• State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 21 subscribers
  • Views 1736 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
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

Mon166: Error 9

Aram Semerjyan

I try to debug my program using dScope.
My RAM is starting from 0x100000 address
and has size of 1MB.
I load monitor from 0x1FE000, and set
interrupt vector table from 0x100000.
After loading executable file, which
is mapped from 0x100000, I set PC = 0x100000
and run step by step pressing <F10>. After first step
the program come on next command: DISWDT.
Next step is not executed and I receive the
monitor error 9: CANNOT WRITE BREAKPOINT VECTOR

How I can debug program on boards without
RAM on 0 address?

  • 0

    I'm having exactly the same problem. Does anyone have a solution for me ?

  • 0

    How I can debug program on boards without RAM on 0 address?

    That's the point. Monitor166 uses NMI interrupt vector to interrupt program execution. This requires that the NMI vector points to the appropriate location in the Monitor166 code. It can be accomplished in two ways:
    1) If there is RAM at addresses 0..0x1FF then the monitor will write the vector on initialization.
    2) if there is programmable ROM at addresses 0..0x1FF then you can program Monitor166 code to that ROM
    3) or you can program interrupt vector redirection table (although I'm not sure if that will work with out-of-the-box Monitor166, look that up in the manuals.)

    - mike

  • 0

    Why don't you say to DScope it should use the ChipSelect for your RAM for adresses from 0x0 ..

    In my case the Flash-CS points to 0x0 .. 0xFFFFF and the RAM-CS points to 0x100000 .. 0x1FFFFF.
    If I use the debugger I use a "start.a66" where CS1(RAM) starts at 0x000000 ("config.inc": BUSCON1 0x000000 too and monitor starts at 0x00A600) and if I make a File for Flash-Download I use a "start.a66" where CS1 starts at 0x100000.
    (of course you have to use for those 2 versions 2 different target-configurations!)
    Maybe it's a little bit dirty but it works fine :)

  • 0

    Hi Aram!

    I see you are using C166 core too.
    Where are you from?
    Maybe we are near?

    Yuri Mirzoyan.
    h_box@rambler.ru