[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Paparazzi-devel] The reason for ACTUATORS_START_DELAY

From: Felix Ruess
Subject: Re: [Paparazzi-devel] The reason for ACTUATORS_START_DELAY
Date: Sat, 6 Apr 2013 01:54:16 +0200

In current master it only (re)sets a debug variable:

But even before that it only set the address (which is only read in I2C driver, never written).
With the "new" I2C driver, the transaction 'type' is changed by the driver state machine in some cases, e.g. if you have a type TxRx (so a transceive) it will set the type to Rx after the transmit is done. Therefore you have to set the type of the transaction every time if you otherwise want to reuse the same transaction.
That is also why the convenience functions i2c_transmit, i2c_receive and i2c_transcieve are usually preferred over the i2c_submit function where you just pass it the transaction.

I don't use the stable versions... basically also work/test with master (quadrotor stuff only on STM32).
But I had the mkk startup problem on my old booz quad sometimes as well, there the startup delay helped.

On Sat, Apr 6, 2013 at 1:33 AM, Sergey Krukowski <address@hidden> wrote:
The mkk_init initializes i2c structures and adresses, which is actually essential. So if the reinitialization helps, the values could be corrupted at some point.
Should also mention, I've never had such troubles with mkk actuators on LPC architecture.
Felix, with here you mean the current stable version or the master? And on what architecture?
My code is based on master, but not sure if have the latest stm i2c fixes, will check out then.


Paparazzi-devel mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]