Re: [xpcc-dev] Device description generation

Hi there, > I checked the ITG3200 driver, and it does what I currently do and > wanted to avoid with a custom transaction, namely that you have to > arrange the data you want to send after the register address in > memory. This either needs a copy, or you have to put the data directly > in the

Re: [xpcc-dev] Device description generation

Hi, I checked the ITG3000 driver, and it does what I currently do and wanted to avoid with a custom transaction, namely that you have to arrange the data you want to send after the register address in memory. This either needs a copy, or you have to put the data directly in the scratch array,

Re: [xpcc-dev] Device description generation

Hi, > First, it is kind of awkward that I'm working with a "random" branch > of xpcc, in that I don't know where to apply bugfixes (I found a few > minor ones) so that they get back to my branch. Should I fork xpcc and > create a new "working" branch from master, and merge in the stm32f103 >

Re: [xpcc-dev] Device description generation

Hi, > I started a driver for the MPU 9250, however I have a problem, the I2C > connection doesn't seem to be working at all. > > I have this method on the driver: > """ > xpcc::ResumableResult alive() { >return this->ping(); > } > """ > which I call in main like this (I only use blocking

Re: [xpcc-dev] Device description generation

Hi! >> I have these initializations for the I2C and the Gpio pins: >> """ >> I2cMaster2::initialize(); >> >> GpioB10::connect(I2cMaster2::Scl); >> GpioB11::connect(I2cMaster2::Sda); >> """ >> >> Do I need anything else? > > No, although we usually do SDA connect, SCL connect,

Re: [xpcc-dev] Device description generation

> I'll probably be back with more questions soon... :) And here I am! I have several things to ask. First, it is kind of awkward that I'm working with a "random" branch of xpcc, in that I don't know where to apply bugfixes (I found a few minor ones) so that they get back to my branch. Should I

Re: [xpcc-dev] Device description generation

Hi Antal, I barely have an internet connection here (im CDU-Wahlkreis) so I can't link to Github because loading is too slooow. Just ack-grep for the keywords in you xpcc repo and you'll find the code. > I found a weird problem, If I update the LCD in a loop (with or > without sleep)

Re: [xpcc-dev] Device description generation

Hi! I really appreciate your answers, they are great help to me :) We have already exchanged a few emails with Strongly-typed, and I'm using 48MHz too for now. I started a driver for the MPU 9250, however I have a problem, the I2C connection doesn't seem to be working at all. I have this

Re: [xpcc-dev] Device description generation

Hi! I just got to try it, and it works if I remove the "systemClock::enable();" line, otherwise it is stuck in that call. Is that bad? I also noticed there's a long (~1s) start-up time (when powering on the device) and looked at the listing, and noticed that the code is copied to RAM. Are these

Re: [xpcc-dev] Device description generation

Hi! A few things work now mostly (LCD, buttons, leds). Now I have to interface with an MPU9250 gyro/accelerometer/compass via I2C, but the I2C examples are all a bit complex as they use premade modules, so I can't yet figure out how to communicate with I2C. Any pointers? 2015-12-28 19:22

Re: [xpcc-dev] Device description generation

Hi, I’ve created a branch with a compilable STM32F103RC example: https://github.com/salkinium/xpcc/blob/feature/stm32f103_support_experimental/examples/stm32f103rc/blink/main.cpp The fastest clock configuration from internal clock is only 64MHz (8MHz / 2 * 16) and NOT 72MHz, which is the max.

Re: [xpcc-dev] Device description generation

I can't get it working yet, the compiler complains that it can't find the xpcc::stm32::Clock type. Here is what I'm trying: http://pastebin.com/g3XdN0K9 (I intentionally left out the enablePll and switchToPll calls, as those generated errors too) Here's the error: main.cpp:7:22: error: 'Clock'