you can still debug without changing the the location, i do this without issues.
Are you using chibistudio and open ocd ?
Bootloader vector table problem Topic is solved
Moderator: RoccoMarco
Re: Bootloader vector table problem
Hmm, thats what I thought you should be able to do. Have you done this by first doing a complete erase of your flash device (i.e. no bootloader or 'original' vector table)
Im running on a linux machine using openOCD and eclipse with the plugin
Im wondering if it might be something to with my arm compiler version. Are you able to tell me what version you are using? Im building with arm-none-eabi-gcc version 4.7.4 20140401
Thanks
Im running on a linux machine using openOCD and eclipse with the plugin
Im wondering if it might be something to with my arm compiler version. Are you able to tell me what version you are using? Im building with arm-none-eabi-gcc version 4.7.4 20140401
Thanks
Re: Bootloader vector table problem
I have now tried with gcc 4.9 and 5.2 with the same problem. All works fine if I have bootloader and app programmed but not when I erase bootloader 
I suspect this is how it is but most people wouldn't have realised, presumably openOCD will only erase what it is about to programme, whereas I have been doing "stm32f1x mass_erase 0" to erase all of flash
I suspect this is how it is but most people wouldn't have realised, presumably openOCD will only erase what it is about to programme, whereas I have been doing "stm32f1x mass_erase 0" to erase all of flash
Re: Bootloader vector table problem
doddi wrote:I have now tried with gcc 4.9 and 5.2 with the same problem. All works fine if I have bootloader and app programmed but not when I erase bootloader
you need bootloader programmed underneath
i'm using 4.9
Re: Bootloader vector table problem
Tabulous wrote:doddi wrote:I have now tried with gcc 4.9 and 5.2 with the same problem. All works fine if I have bootloader and app programmed but not when I erase bootloader
you need bootloader programmed underneath
i'm using 4.9
Thanks for the input, I think I have been chasing my tail with another issue in that case!
Can you tell me which complete version of gcc you have please? Mine is 4.9.3 and last time I had other runtime issues for mounting the SD card, some of the function in libgcc arent working correctly with chibios
Thanks
Re: Bootloader vector table problem
It turns out it is something to do with gcc 4.9.
Although it compiles there doesnt seem to be a strcmp available and it is this that is causing the unhandled_exception. It is probably an issue with the rules.ld file that I am using as part of the ChibiOS I was given for this project.
I dont have time to investigate any further but 4.7.4 seems to work fine. I have read in a few places that it might have something to do with eh_frame's?
Although it compiles there doesnt seem to be a strcmp available and it is this that is causing the unhandled_exception. It is probably an issue with the rules.ld file that I am using as part of the ChibiOS I was given for this project.
I dont have time to investigate any further but 4.7.4 seems to work fine. I have read in a few places that it might have something to do with eh_frame's?