Re: Unhandled interrupt (3) occurred when porting mynewt to other board

Hi Aditi, Should porting patch as will as using GitHub PR? Thanks, Louie. 2017-03-09 18:32 GMT+08:00 aditi hilbert : > Hi Louie, > > Thank you for fixing a bug! The best way is to submit a PR on github. For > now you can issue the PR against the develop branch. Eventually we

Re: Unhandled interrupt (3) occurred when porting mynewt to other board

Hi Louie, Thank you for fixing a bug! The best way is to submit a PR on github. For now you can issue the PR against the develop branch. Eventually we will only have feature or subsystem branches, so the PRs will be submitted against the applicable branch or master. Right now we have the

Re: Unhandled interrupt (3) occurred when porting mynewt to other board

Hi Marko, Thanks for your help, your tips are very useful, after some retry and your tips, I finally let blinky work properly on STM32F429. I'm now getting forward to slinky and try to make it OK. Another question is, I found a bug that isn't directly related with porting stuff, if I want to

Re: Unhandled interrupt (3) occurred when porting mynewt to other board

Hi Louie, thanks for the pointer to code. I can see that the startup code is probably what you should look at. Contrast and compare those against the file stm32f4discovery uses. Here are few things I noticed: interrupt vector holds ‘__StackTop’ as the pointer to initial stack. I notice in

Re: Unhandled interrupt (3) occurred when porting mynewt to other board

Hi Marko, Yep, you are right, I got some bad setting in linker script with _estack value. I'm now using the branch here: https://github.com/grapherd/incubator-mynewt-core which derived from master: 8cf8f54dcf4cb2d I've trying to give the space for _estack, it CCM or at the end of the RAM, (it

Re: Unhandled interrupt (3) occurred when porting mynewt to other board

Interrupt 3 means Hard fault. Cursory read of the register dump included seems to indicate ‘unaligned access’. And the fault happens within context switching code. Which git branch are you using? Or git tag. I might be able to give more hints if I knew which version of HAL_CM4.S, line 163 you

Re: Unhandled interrupt (3) occurred when porting mynewt to other board

Hi Sterling, Thanks for your reply, this is the info I got from debugger and serials: serials core dump: 0:Unhandled interrupt (3), exception sp 0x2002ff90 0: r0:0x r1:0x20001144 r2:0x r3:0x200012b0 0: r4:0x r5:0x r6:0x20001144 r7:0x08023684 0:

Re: Unhandled interrupt (3) occurred when porting mynewt to other board

Hi Louie, Excellent! We’d love the port when you’re done. That usually means a crash of some type has occurred? Can you attach a debugger, you should be able to see a stack trace (similarly - if you can get the console attached, it should *fingers-crossed* dump to console.)

Unhandled interrupt (3) occurred when porting mynewt to other board

Hi everyone, I'm now porting mynewt to STM32F429, and this board has the same MCU and CPU with the board STM32F07 which mynewt have already supported. I have now using blinky and slinky to verify the correctness of porting, but encounter the problem that serial output "Unhandled interrupt (3)"