Hello,
when compiling example for the platform linux, e.g. the logger example
on the develop branch scons always displays the following message:
scons: warning: Two different environments were specified for target
xpcc/architecture/platform.hpp,
but they appear to have the same action: template_action(target,
source, env)
File
"/home/thor/rca/season_2015/xpcc/scons/site_tools/platform_tools.py",
line 220, in platform_tools_generate
Can someone check if this is the desired behaviour or fix the warning?
Best Regards and a Happy New year,
Thorsten
Hi!
I've started using your great xpcc-library 3 years ago, studied it and
learned a lot, exclusively about templates und just great, comfortable
code. Until my Hardware experiments, i've written several drivers (for
avr).
Some of them are finished and unit-tested, some of them are in progress.
Of course, I've mentioned your code convention and design rules.
Now it's time for me to colaborate my very first software-project :), so
i've studied git.
As i understand, i would open a Branch, push my code, and hopefully one
day, everyone is happy and it get's merged. Right?
Hello again! And see you later,
Thomas Sommer
Hi,
it seems that there are currently no device files provided for the
STM32F100 family. It is advised to edit xpcc/tools/DeviceFileGenerator
to modify existing or add new devices. However, it is unclear to me how
to do so.
Can you provide me with some help to add support for the STM32F100 family?
Kind regards,
Jonas
Hello,
I've just noticed, that our definition of interrupt vectors for stm32
micro controllers is not easy to follow.
Do we get the names and definition of the interrupt vectors from the
data sheet or from some auto-generated xml structures?
As you can see in the previous structure on current master branch there
are differences in definition of interrupt vectors in startup code for
several devices, where not all of them are represented in the current
structure on develop.
The pending problem:
There is the interrupt vector CAN1_TX_IRQHandler, which is called
USB_HP_CAN1_TX_IRQHandler on some devices (may be different inside same
families=targets like connectivity line devices?).
Noticed, unfortunately at runtime, while testing can driver on
STM32F3, which does not fit to interrupt vector names in startup code.
Maybe you have already thought of any automated solutions producing
errors at compile-time and ensuring correctness here?
greetings
Georgi
PS: some file paths
Maybe the more tested and maybe more correct version on master branch
(SHA-1: 21ee647a1900177d71e3722db3846b017790aeb9)
xpcc\src\xpcc\architecture\platform\cortex_m3\stm32\stm32f1\startup\startup.c
xpcc\src\xpcc\architecture\platform\cortex_m3\stm32\stm32f2_f4\startup\startup.c
The current version on develop (SHA-1:
471065ecde15b4983c6633815108ad347eb9524e)
xpcc\src\xpcc\architecture\platform\core\cortex\startup.c.in
xpcc\src\xpcc\architecture\platform\core\cortex\stm32\...
xpcc\src\xpcc\architecture\generated_platform_xxx\core\cortex
xpcc\src\xpcc\architecture\platform\peripheral\can\stm32\can.cpp.in
xpcc\src\xpcc\architecture\generated_platform_stm32f303cc\peripheral\can\stm32\can_1.cpp
Hi devs,
you added the sdl_display.hpp to the example folder
examples/linux/gui/sdl_display.hpp
But the SDL display already existed as class of xpcc under #include
<xpcc/architecture/platform/hosted/linux/display/sdl_display.hpp>. The
additional functionality of this class should have been added there and
then this class should be included in the example instead of copying the
class files to the example folder.
Best Regards,
Thorsten
Hi,
unfortunately, the archive of this mailing list is not indexed by google
because of the `http://mailman.rwth-aachen.de/robots.txt`.
This makes it difficult for people searching for xpcc to find any
information present on our list.
Since I do not see any easy way to change this I would like to mirror
our mailing list at Gmane: http://gmane.org/about.php
Are there any objections?
Kevin
Hi,
I was greatly interested in the talk you gave at FOSDEM this weekend.
Many thanks for that!
We have a project in the works based around an LPC1768 part. Looking at
the wiki / git repo I see some support for the LPC1343, although not the
LPC1768, and both parts seem to be based on an ARM Cortex-M3
I was wondering if there is any out-of-the-box support for the LPX17xx
series, or if you could comment on what would be involved for me to add
this?
(Presumably as a start there would need to be a new XML configuration
file, as you mentioned in the talk? Also I'm very interested in I2C
driver support)
Thanks!
Alex Lennon
http://www.dynamicdevices.co.uk
are now available on this link:
https://www.dropbox.com/s/mocxy5jbrth68ad/xml.zip
Both AVR and STM32 devices have been updated to include the latest chips.
Noteworthy additions are the STM32F030 and the STM32F429.
Happy programming,
Niklas
