indart-stx problem
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2004-02-23 9:16 PM
This discussion is locked. Please start a new topic to ask your question.
3 REPLIES 3
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2004-02-18 9:45 PM
Posted on February 19, 2004 at 06:45
dear sir,
while I debug my project(device St7Flite29F2B6) with indart-stx/lit2, there is a problem as follows: Starting debug session... -> Emulator reset (LPT1)... Disconnected from the GDI Debug Instrument. Connected to the GDI Debug Instrument. done. Opening application E:\project\ST7WHM.elf... done. -> Chip-reset... ** Application stopped: -> Run... ** Application stopped: Starting program: Program received signal SIGTRAP, Trace/breakpoint trap. 0xe000 in __stext () -> Continue... ** Application stopped: Continuing. Program received signal SIGTRAP, Trace/breakpoint trap. 0xe000 in __stext () I mean I can not run the programm by pressing F5(continue) Key( I use my own target boad wiht resonator 8Mhz. But if I use internal RC oscillator, I can run the program. Can anybody help me solve this problem. Thanks a lot! perryOptions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2004-02-22 10:13 PM
Posted on February 23, 2004 at 07:13
Hi Perry,
I could see your problem with inDART-STX and the LITE2 device on my PC. I got this error when I set the Watchdog Option Byte to ''Hardware''. This setting will keep on resetting the application if you do not have a software routine that refreshes the Watchdog timer register. Let us know if you get this issue fixed (support@softecmicro.com). Regards.Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2004-02-23 9:16 PM
Posted on February 24, 2004 at 06:16
Hello
I'm using ST72F521, cosmic and I had also this problem. I found out that: 1. declartion pointer and initialize it out of modulefor ex.: const char nv_ram[]={,,,,,,,,,}; char *ptr=nv_ram; main() { } my soulion was: const char nv_ram[]={,,,,,,,,,}; char *ptr; main() { ptr=nv_ram; while (1) { ,,,,,,,,, } } It works good. 2. also be carful with initialized static decalarion in subroutin. it also cause run time error.