Re: [xpcc-dev] Hard fault debugging

2016-01-13 Thread Niklas Hauser
Hi, >> I and other people from the robotics club had a look at your traces, but we >> could not think of anything, that would cause them. > Thanks for looking into it! That's probably because they are caused by > the hardware (which I suspected all along). Regarding the hardfault: Have a look at

Re: [xpcc-dev] Hard fault debugging

2016-01-13 Thread Szabó Antal
2016-01-13 20:34 GMT+01:00 Kevin Laeufer : > I and other people from the robotics club had a look at your traces, but we > could not think of anything, that would cause them. Thanks for looking into it! That's probably because they are caused by the hardware (which I suspected all along). _

Re: [xpcc-dev] Hard fault debugging

2016-01-13 Thread Kevin Laeufer
Hi, On 13/01/16 20:09, Szabó Antal wrote: Hi, We modified the board to follow what you suggested, but there wasn't any real improvement. However, lowering the system frequency to 32 MHz "solved" all the problems, the test program correctly ran overnight without crashing. I don't exactly know wh

Re: [xpcc-dev] Hard fault debugging

2016-01-13 Thread Szabó Antal
Hi, We modified the board to follow what you suggested, but there wasn't any real improvement. However, lowering the system frequency to 32 MHz "solved" all the problems, the test program correctly ran overnight without crashing. I don't exactly know what causes this, possibly some kind of interfe

Re: [xpcc-dev] Hard fault debugging

2016-01-08 Thread Szabó Antal
Disclaimer: I didn't yet rewire the whole thing according to the hardware development doc (I actually don't do the electronic part, but told the guy who does to fix it according to the doc), so this might be caused by electronic errors. 2016-01-09 0:37 GMT+01:00 Szabó Antal : > I got another one:

Re: [xpcc-dev] Hard fault debugging

2016-01-08 Thread Szabó Antal
I got another one: (gdb) where #0 _hardFaultHandler (ctx=0x2000bed0) at build\libxpcc\generated_platform\driver\core\cortex\hard_fault_handler.cpp:39 #1 #2 0x080016be in I2C2_EV_IRQHandler () at build\libxpcc\generated_platform\driver\i2c\stm32\i2c_master_2.cpp:352 #3 #4 0x08000a24

[xpcc-dev] Hard fault debugging

2016-01-08 Thread Szabó Antal
Hi! Thanks for the advice in the previous thread. I fired up gdb, and ran the program several times. This is the stack trace I get most of the time: (gdb) where #0 _hardFaultHandler (ctx=0x2000bea0) at build\libxpcc\generated_platform\driver\core\cortex\hard_fault_handler.cpp:39 #1 #2 0x