Re: [xpcc-dev] Device description file sources

On Mon, Mar 26, 2018 at 4:46 PM, Hauser, Niklas Lennart wrote: > I published my blog post on extracting and using this data here, btw: > http://blog.salkinium.com/modm-devices/ Thanks, I will definitely read it! ___

Re: [xpcc-dev] Device description file sources

On Mon, Feb 12, 2018 at 10:54 PM, Niklas Hauser wrote: > The advantage of the CMSIS header files over the SVD files is that everyone > actually uses them to compile code. > The SVD files originally were only for the Keil IDE debugger to assign > meaning to IO memory

Re: [xpcc-dev] Error with I2C eeprom

Hi, >> Ok, maybe another poke in the dark: >> There is this thing where page write (= writes > 1B) have to be aligned to >> the page size (128B for my chip): >> […] >> Maybe that could explain why you would get 0xFF as the second byte? > > Just as a follow-up on this, I just tried this, and it

Re: [xpcc-dev] New xpcc.io website

Hi, It's a really nice improvement over the previous one! I like that there's much more explanation of what xpcc is / how it works, and also, it looks good :) 2016-04-28 23:44 GMT+02:00 Niklas Hauser : > Hi, > > xpcc has a new and improved website (for a while now

Re: [xpcc-dev] Error with I2C eeprom

Hi, > Which specific I2C EEPROM chip do you use? I'm using a 24FC128, specifically chosen because the driver mentioned this family. > You can debug the SoftwareI2C driver by adapting these lines: >

[xpcc-dev] Hard fault debugging

Hi! Thanks for the advice in the previous thread. I fired up gdb, and ran the program several times. This is the stack trace I get most of the time: (gdb) where #0 _hardFaultHandler (ctx=0x2000bea0) at build\libxpcc\generated_platform\driver\core\cortex\hard_fault_handler.cpp:39 #1 #2

Re: [xpcc-dev] Hard fault debugging

{ 354 DEBUG_STREAM("enable buffers"); 355 I2C2->CR2 |= I2C_CR2_ITBUFEN; 356 } which doesn't make much sense to me, as that line is just arithmetic comparisons. 2016-01-09 0:19 GMT+01:00 Szab

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! >> 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! 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

ied to RAM. Are these related? Why is this needed? 2015-12-25 0:55 GMT+01:00 Szabó Antal <szabo.antal...@gmail.com>: > Thanks, I'll try this. > > Happy Holidays to you and everyone else too :) > > Antal Szabó > > 2015. dec. 25. de. 12:32 ezt írta ("Niklas Hauser" > <

Re: [xpcc-dev] Device description generation

:00 Szabó Antal <szabo.antal...@gmail.com>: > 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 &g

Re: [xpcc-dev] Device description generation

' in namespace 'xpcc::stm32' does not name a type typedef xpcc::stm32::Clock C; I also don't know what should the parameters be for enablePll. Can you please provide a small example like mine, with setting the pll from internal oscillator, that at least compiles? 2015-12-23 12:37 GMT+01:00 Szabó