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

show debug information

Hello,

I want to install printf("hallo welt %d\n", intvariable) in my code for debug information. Where can I see this information when I have no usart? Is there a command line in uvision where I can see this?

Bernd

  • Where can I see this information when I have no usart?

    Since you didn't specify a processor type, it's a bit hard to give a definite answer. It depends on the type of chip and emulator.

    You may be able to modify the printf() function to use a different type of interface, or emulate a UART in software on one of the processor pins (fairly easy to do for transmit, but quite a bit of work if you want to receive anything).

  • I don't know that it depends on which chip I'm using. I'm working with uvision and ulink2. I have the AT91RM9200, but without using the usart rs232; I've only installed USB - but if there's a way to do that without using a external hardware from the AT91 it would be very nice.

    I only want to transmit values of registers e.g. because I'm not really familiar with ASM (debug information in keil).

    best regards
    Bernd

  • "I'm working with uvision and ulink2"

    The whole point of JTAG is that you no longer have to write code that consumes processor resources in order to "push" debug info to the debugger!

    Intead, you use the debugger to just view register vlaues, variables, etc - and it all just happens by the magic of JTAG!

    I suggest you spend some time reading the uLink and uVision manuals...

  • I don't know that it depends on which chip I'm using
    there is a world of difference between an ARM and a '51. The compilers are, as well, quite different.

    Weik

  • ok - that means I'm on the wrong way with printf(). I have to learn to read the ASM debug information.

    thanks for your answer

    Bernd

  • "I have to learn to read the ASM debug information."

    No - the tools provide Source-Level debug information.

    Again, see the Manuals

    Having said that, it will be a distinct disadvantage if you cannot at least read assembler...