Search found 35 matches

by Laurent
Fri Jan 05, 2018 3:03 pm
Forum: STM32 Support
Topic: My fix in ChibiOS to make LWIP work
Replies: 4
Views: 1183

Re: My fix in ChibiOS to make LWIP work

Nevermind, after investigating more I found that it was caused by another library that we use on top of LWIP.
by Laurent
Fri Jan 05, 2018 1:18 pm
Forum: STM32 Support
Topic: My fix in ChibiOS to make LWIP work
Replies: 4
Views: 1183

Re: My fix in ChibiOS to make LWIP work

Thanks for your quick reply. The current trunk seems to solve this particular problem, although it brings a new one: LWIP breaks on an assert as soon as a second TCP connection is made ( the very first one works flawlessly apparently the first connection appears to break sometimes when receiving dat...
by Laurent
Fri Jan 05, 2018 11:48 am
Forum: STM32 Support
Topic: My fix in ChibiOS to make LWIP work
Replies: 4
Views: 1183

My fix in ChibiOS to make LWIP work

Hi I was testing LWIP with ChibiOS (latest, 17.6.3) on a STM32F107 (Olimex STM32-P107 board, rev. B), and noticed that it didn't work quite well (couldn't ping the IP). After some random trials, I found that I needed to insert a delay right after the call to macStart (in lwipthread.c). After further...
by Laurent
Mon Apr 03, 2017 10:00 am
Forum: STM32 Support
Topic: ChibiOS crashes when my firmware is not at beginning of flash memory
Replies: 32
Views: 6773

Re: ChibiOS crashes when my firmware is not at beginning of flash memory

As I said, I need the small sectors so I can't put the data at the end (16 KB sectors vs 128 KB sectors make a huge difference for me). I added the MSP initial value and reset handler address -- the same values that ChibiOS uses -- at the beginning of sector 0 (at address 0x80000000), and everything...
by Laurent
Thu Mar 30, 2017 2:07 pm
Forum: STM32 Support
Topic: ChibiOS crashes when my firmware is not at beginning of flash memory
Replies: 32
Views: 6773

Re: ChibiOS crashes when my firmware is not at beginning of flash memory

So flash sector 0 can never contain pure data? That's annoying.

You need to have a vectors table at address zero containing at least the reset address and the MSP initial value.

Sorry but I know very little about vectors table, how would I do that?
by Laurent
Thu Mar 30, 2017 1:55 pm
Forum: STM32 Support
Topic: ChibiOS crashes when my firmware is not at beginning of flash memory
Replies: 32
Views: 6773

Re: ChibiOS crashes when my firmware is not at beginning of flash memory

How do you make the STM32 start at that address? I don't know :D All I did was changing the flash start address in linker script and CORTEX_VTOR_INIT, as shown in my first post, and I thought it was enough. Are you saying that the very first thing to run has to be at address 0? In this case, how ca...
by Laurent
Thu Mar 30, 2017 1:48 pm
Forum: STM32 Support
Topic: ChibiOS crashes when my firmware is not at beginning of flash memory
Replies: 32
Views: 6773

Re: ChibiOS crashes when my firmware is not at beginning of flash memory

I imagine you have some kind of bootloader No I don't. I just need the 4 smallest (16KB) flash sectors to store data, and unfortunately those are located at the beginning, that's why I'd like to move my firmware to sector 4 and directly boot there. So no, no other code is run before my firmware is ...
by Laurent
Thu Mar 30, 2017 1:37 pm
Forum: STM32 Support
Topic: ChibiOS crashes when my firmware is not at beginning of flash memory
Replies: 32
Views: 6773

Re: ChibiOS crashes when my firmware is not at beginning of flash memory

Thanks for the very quick reply.

SCB->VTOR correctly contains 0x10000 after chSysInit().
by Laurent
Thu Mar 30, 2017 1:03 pm
Forum: STM32 Support
Topic: ChibiOS crashes when my firmware is not at beginning of flash memory
Replies: 32
Views: 6773

ChibiOS crashes when my firmware is not at beginning of flash memory

Hi After I moved my firmware to sector 4 of flash memory, ChibiOS stopped working. I changed this in linker script: flash : org = 0x08010000, len = 448k And added this in chconf.h: #define CORTEX_VTOR_INIT 0x00010000 I erased the whole device memory, just in case. Firmware gets correctly written at ...

Go to advanced search