Interface and Connectivity ICs
MEMS and Sensors
Analog and Audio
EMI Filtering and Signal Conditioning
Power Management and Motor Control
SPC5 Automotive MCUs
ST25 NFC/RFID Tags and Readers
Switches and Multiplexers
STM32 MCUs Community
MEMS and Sensors Community
Automotive MCUs Community
STM8 MCUs Community
Help the community
Share your activities
Contribute your knowledge
About this community
to create and rate content, and to follow, bookmark, and share content with other members.
Question asked by
on Apr 28, 2006
on Apr 28, 2006 by 12428
Show 0 Likes
No one else has this question
Mark as assumed answered
This content has been marked as final.
Show 2 comments
(Required, will not be published)
Apr 26, 2006 10:56 AM
Hi I want to see my interrupts in ZAP written in C.
First I created a interrupt file such that file.int by using dump in menu as told in manuel.But as default ZAP uses its file not mine.And how can I load my interrupt file to ZAP because it only allows me to save it not load
Second after I load my file to ZAP for interrupt I want to use see my file using breakpoint.
Third I used an eeprom variable.I decleared a space in link file such that
.eeprom -b0x1000 but when I was watching ZAP I saw an error for EECSR.Although I changed address of EECSR in eeprom.i file,compiler didn't change or I couldn't see.I saw _d_d+12 whereas my EECSR was _d_d.
Do you know why I can't see 0x02c(_d_d+12) address instead of 0x020
Thanks in advance
[ This message was edited by: ege_deu on 26-04-2006 14:29 ]
Show 0 Likes
Apr 28, 2006 6:34 AM
can you please contact me offline at luca dot ubiali at cosmic dot fr ?
Waiting for that, here are some answers:
1) To use a specific interrupt table in ZAP you go in the menu Setup -> Interrupts -> Select Table
2) .. I want to use see my file using breakpoint ?? I can't understand what you want to do here, but, if you want to put a breakpoint in your int routine, just open the associated source file and doule click on any line with the green dot in front of it.
3) Make sure if this is a problem in the compiler/source part or in the debugger part by looking at the absolute listings: if the address is correct in the abs listing, the problem is probably that the debugger is using some files that are not those you intended: check the paths. If the address is wrong in the abs listing, check your source files.
Show 0 Likes
Retrieving data ...
2018 STM32 Wish List
STM32-C2C (Cellular to Cloud) Web Concierge Portal
STM32F769I-DISCO: No audio output from wm8994
STM32CubeMX V4.24.0 code generation failure (bug report)
CubeMX SDIO DMA FatFS configuration