Page 4 of 4

Re: Starting from scratch again... On SW4STM32 now

Posted: Mon Oct 17, 2016 8:59 am
by Chudik
Finally understood that for correct index after any changes in "root" path index->Freshen all files must be done.
Now not need to have ChibiStudio folder for having access to Chibios.

Re: Starting from scratch again... On SW4STM32 now

Posted: Tue Oct 25, 2016 4:12 am
by Chudik
Giovanni
One thing makes a big trouble
I have same project and same environment on two computers (almost - on one computer I have partition E: for ChibiStudio and on another substitute for this drive)
On one computer I have no problem.
On another project uses wrong header file for defining such things like GPIOA (in thread "Blinker").
For unknown for me reason it uses KINETIS mk20d5.h instead of ST stm32l152xe.h

If I physically delete directory KINETIS, it uses pal_lld.h that redefines GPIOA, but does not redefine GPIOA_BASE

Any ideas?

Re: Starting from scratch again... On SW4STM32 now

Posted: Tue Oct 25, 2016 7:14 am
by Giovanni
Frankly no idea...

Giovanni

Re: Starting from scratch again... On SW4STM32 now

Posted: Fri Oct 28, 2016 2:49 am
by Chudik
The interesting thing that project compiles and works. However, the fact, that for GPIOA it shows another .h file and can't find GPIOA_BASE scares me.

Re: Starting from scratch again... On SW4STM32 now

Posted: Fri Nov 18, 2016 12:23 am
by Chudik
Regarding debug interface for the custom board with this IDE

For the reference of all ports and required peripheral I used CubeMX and created empty project for the board - just initialization. After compilation loaded to to my custom board. The IDE created .cfg file for debugging interface and I copied it to my ChibiOS project in this IDE.

Seems like this is the easiest way.

And using CubeMX helped me to understand what needed to add to configuration XML file for my board.

Re: Starting from scratch again... On SW4STM32 now

Posted: Mon Nov 21, 2016 7:53 pm
by Chudik
Amount of problems for adapting ChibiOS (really great RTOS) for another environment with a custom board exceeds all acceptable limits :(
Can't spend another 2-3 months to get basic functionality (LED blink + Shell). I'm going to switch to another system that is not so great that been used by my buddy for MSP430. It is actually a simple scheduler and it uses just a couple HW related peripherals that could be transferred to STM32.

Will be glad if anybody find this thread useful and solve the problems I meat on this way.