Activity
From 04/17/2015 to 05/16/2015
04/30/2015
- MW 07:53 AM Software Development: RE: Bare-metal interrupt handling working only in debugger
- Hi Alex,
Glad you solved your issue, sorry we didn't provide much help. We don't have a lot of folks trying to do Bare-Metal (and we don't do it often either).
-Mike - AL 06:22 AM Software Development: RE: Bare-metal interrupt handling working only in debugger
- No, that was obviously not the reason. The unhosted and hosted linker scripts do link against different libraries but that only seems matters for stdio. I was able to solve the problem by rewritting everything from scratch. The way I was...
04/28/2015
- AL 03:50 PM Software Development: RE: Bare-metal interrupt handling working only in debugger
- I am now thinking that I might have to use the unhosted version of the linker script (even though it worked just fine for compiling programs without interrupt handlers).
Might be that the Sourcery compiler does something 'weird' with th... - AL 02:36 PM Software Development: RE: Bare-metal interrupt handling working only in debugger
- Hi Mike,
That address is indeed the base of the interrupt table. I have been using it without any problem with other programs, which run just fine and which were compiled using the same linker script (which always inserts a vector tab... - MW 11:20 AM Software Development: RE: Bare-metal interrupt handling working only in debugger
- I personally haven't tried to do this before, but isn't address 0x30000000 the base of your interrupt vector table? Is that the actual runtime entry point (a jump instruction to the CRT) or is that an address for a reset interrupt? Can...
- Hello,
I am using the MitySOM Dev Kit and I want to use interrupts in a bare-metal
application. To that effect I wrote a 'small' program where I enable the private
timer (and the interrupt bit as well) and wrote an IRQ handler.
...