Search found 14 matches

by mikeprotts
Tue Jul 16, 2019 4:34 pm
Forum: General Support
Topic: why i wasn't able to debug the demo code while i can only flash it?
Replies: 11
Views: 97

Re: why i wasn't able to debug the demo code while i can only flash it?

Using gdb manually, I need to use hb (hardware assisted break) rather than b (normal breaK) for the F767 board.

I don't know how to do that from ChibiStudio as I've not used it yet.

Mike
by mikeprotts
Fri Jul 12, 2019 12:59 pm
Forum: STM32 Support
Topic: Unhandled exception - how to debug
Replies: 19
Views: 177

Re: Unhandled exception - how to debug

I seem to be ok for now with these settings. My lwipopts.h and lwippools.h are attached. The pool sizes were bigger to start with, but i reduced them based on the usage indicated by lwip stats.
by mikeprotts
Fri Jul 12, 2019 12:33 pm
Forum: STM32 Support
Topic: Unhandled exception - how to debug
Replies: 19
Views: 177

Re: Unhandled exception - how to debug

I had problems with interrupt handlers when I hadn't allocated enough to the stack, or when I'd not left enough free core or heap. It took a while for me to realise that the unhandled exception was nothing to do with VectorF8, but somewhere else in the code, in my case often in the network interrupt...
by mikeprotts
Fri Jul 12, 2019 11:30 am
Forum: STM32 Support
Topic: Unhandled exception - how to debug
Replies: 19
Views: 177

Re: Unhandled exception - how to debug

VectorF8 is probably not relevant, it's more likely to be out of memory or similar. You may need to reduce usage somewhere, or increase the allocation to the relevant area - at a guess PORT_INT_REQUIRED_STACK may need to be larger.

Mike
by mikeprotts
Fri Jun 21, 2019 8:02 am
Forum: STM32 Support
Topic: GDB debugging.
Replies: 6
Views: 179

Re: GDB debugging.

I struggle with single stepping as I have frequently firing interrupts at high priority. My usual debugging process is to set several breakpoints for the area of code of interest, and just examine the code when it hits these. Often I add another breakpoint for the next line of interest so 'continue'...
by mikeprotts
Thu Jun 06, 2019 12:34 pm
Forum: ChibiOS/HAL
Topic: MPU9250 gives garbage when spiExchange is used but not when spiSend
Replies: 4
Views: 191

Re: MPU9250 gives garbage when spiExchange is used but not when spiSend

I've had issues when I didn't setup the registers correctly - migrating from ChibiOS 3 to 18, and with different boards having different configuration requirements, so my first suggestion is to check the configuration again. It's possible you've ended up with a wrong data size setting. The second pr...
by mikeprotts
Thu Jun 06, 2019 12:25 pm
Forum: ChibiOS/HAL
Topic: Determining RAM available at compile or run time
Replies: 3
Views: 147

Re: Determining RAM available at compile or run time

Thanks for these tips. I'm moving data from ISR to buffers to allow for network latency, so the hal queues idea makes sense. I'll try chCoreAlloc to create the appropriate size, and then create my pool. As I should be able to do this before I start anything time critical, it shouldn't need too much ...
by mikeprotts
Fri May 31, 2019 12:44 pm
Forum: ChibiOS/RT
Topic: Problem compiling ChibiOS for QMK
Replies: 3
Views: 225

Re: Problem compiling ChibiOS for QMK

My suggestion would be to get the build environment set up for whichever version of ChibiOS was used last time (probably ChibiOS 3 - https://sourceforge.net/projects/chibios/files/ChibiOS%20GPL3/Version%203.0.5/) and make sure that builds cleanly. Then you can try with the current ChibiOS using a ne...
by mikeprotts
Fri May 31, 2019 11:59 am
Forum: ChibiOS/HAL
Topic: Determining RAM available at compile or run time
Replies: 3
Views: 147

Determining RAM available at compile or run time

I want to be able to allocate a large static circular buffer, where I will use as much RAM as I can up to a certain amount, e.g. I might want 64KB, but if there is not sufficient RAM I'd allocate maybe 16KB. The buffer is accessed in 2KB chunks, using an array of pointers. I want to make the code po...
by mikeprotts
Fri Jan 11, 2019 12:29 pm
Forum: User Projects
Topic: lwIP TCP client
Replies: 1
Views: 354

Re: lwIP TCP client

From ChibiOS_18.2.1/ext/lwip/src/include/lwip/err.h, -4 would be a routing problem. I assume the * markers for IP addess are within the same subnet (otherwise you'll need the gateway address set). I'd suggest moving most variables to global and declaring as static. Also for the client port you know ...

Go to advanced search