07-13-2016, 06:49 PM
i think that sensor might actually work...
that device tree says for gsensor:
gsensor_twi_addr = <0x0000001d>;
and the datasheet for the ADXL345 says
if you get one, let us know if it works.
that device tree says for gsensor:
gsensor_twi_addr = <0x0000001d>;
and the datasheet for the ADXL345 says
Quote:I2Cnotice the address 0x1D part.
With CS tied high to VDD I/O, the ADXL345 is in I2C mode, requiring a simple 2-wire connection as shown in . The ADXL345 conforms to the UM10204 I2C-Bus Specification and User Manual, Rev. 03—19 June 2007, available from NXP Semiconductor. It supports standard (100 kHz) and fast (400 kHz) data transfer modes if the timing parameters given in and are met. Single- or multiple-byte reads/writes are supported, as shown in . With the SDO/ALT ADDRESS pin high, the 7-bit I2C address for the device is 0x1D, followed by the R/Figure 8Table 11Figure 10Figure 9W bit. This translates to 0x3A for a write and 0x3B for a read. An alternate I2C address of 0x53 (followed by the R/W bit) can be chosen by grounding the SDO/ALT ADDRESS pin (Pin 12). This translates to 0xA6 for a write and 0xA7 for a read.
if you get one, let us know if it works.