2007-09-16 11:11 PM
2007-09-13 06:19 AM
Hello,
I'm using the IAR-EWARM over the parallel Wiggler-Interface. The processor is an STR710. Unfortunately, the debug interface is terribly slow. It lasts tens of seconds for start, and for reset too. Is there any faster Interface? My second question is for the UART. I don't understand the interrupts. Are the Interrupts level or edge-sensitive? How can I reset the bit 9 of the RXBuf. The following does'nt work: uint16_t int_flags=UART_FlagStatus(UART1); uint8_t data=UART1->RxBUFR; Are there any more sophisticated sample codes, as in the Softlibrary examples? Many thanks, Steffen Netz2007-09-13 07:06 PM
I'm using IAR EWARM with Macraigor wiggler, the MCU is STR7 It takes a few seconds to start a debug session and download program into RAM. It takes a bit longer to program flash - a few seconds for erase plus flash programming at a rate of about 10 kbytes per second. I'd say it's reasonable.
About the other question: the interrupts are level-sensitive. Don't know about the 9th bit, never used it. Have a look at my driver for interrupt-driven UART operation. - mike ________________ Attachments : rs232.zip : https://st--c.eu10.content.force.com/sfc/dist/version/download/?oid=00Db0000000YtG6&ids=0680X000006HtBj&d=%2Fa%2F0X0000000aK5%2F5kmP5OsuuOID3VoM3rQDkTO0FCmtdxAwevneRqC6vSk&asPdf=false2007-09-13 10:20 PM
Thx, mike :D
I've found the following times: Start from Editor ( Make & Debug without compile) : 35 Sec Reset from Debugger : 17 Sec This is loooooooooong! O.K. Any idea? regards, Steffen2007-09-14 04:01 AM
You could try disabling debugger plugins. For example, I found that the Stack plugin slows down single-stepping considerably.
Another thing is that the ARM CPU has only two hardware breakpoints. When the debugger is out of hardware breakpoints, it will fall back to single-stepping. Check if that affects you. Also if you have huge arrays in the Watch window, the debugger will take its time to read those.