What is my i2c device slave address?

[Raul Piper]

>Thanks for the manual.  Now I believe the client address of this chip
should be set to either 0x4a or 0x4b. The only problem left is how do I
>know what is the ADDR_SEL status? Since I see in the driver code there is
no a line that is setting up this pin, so can I assume that the >ADDR_SEL
is hard-wired on my board and I just need to ask my hardware engineer to do
a measure on the pin, right?

You have to see the h/w schematic of the controller for this.Other way is
i2c detect utility which I mentioned above.Run it and see if the address is
0x4a or 0x4b.
Yes you can definitely ask the hardware engineer.


>Another not so related thing is that I also noticed that there are still
other two addresses  that can be used to do firmware upgrading. I just
>read this from the driver code and also want to know if it is necessary in
my case to concern about downloading a firmware to the chip? I >really hope
things won't go such complicated and the chip should simplify work as long
as I correctly setup and load the linux driver for it.  >Do you also has an
idea about this?

I think that means your controller has a bootloader (and hence other two
address - may be one for ADDR_SEL -  high and another for ADDR_SEL - low )
and the firmware can be updated via Host as well.Are you using any kernel
firmware update interface?something like this :
http://www.makelinux.net/ldd3/chp-14-sect-8 .n that case you must be having
the bin file which needs to be placed in the /etc/firmware directory from
which your host will pick the file and update the cntroller firmware.But be
aware that you must know what protocol is being used by your hardware for
this updation(ymodem,xmodem,etc).



On Sat, Aug 8, 2015 at 7:59 PM, Woody Wu <narkewoody at gmail.com> wrote:

> Hi Raul,
>
> Thanks for the manual.  Now I believe the client address of this chip
> should be set to either 0x4a or 0x4b. The only problem left is how do I
> know what is the ADDR_SEL status? Since I see in the driver code there is
> no a line that is setting up this pin, so can I assume that the ADDR_SEL is
> hard-wired on my board and I just need to ask my hardware engineer to do a
> measure on the pin, right?
>
> Another not so related thing is that I also noticed that there are still
> other two addresses  that can be used to do firmware upgrading. I just read
> this from the driver code and also want to know if it is necessary in my
> case to concern about downloading a firmware to the chip? I really hope
> things won't go such complicated and the chip should simplify work as long
> as I correctly setup and load the linux driver for it.  Do you also has an
> idea about this?
>
> Many thanks.
> -woody
>
>
> On Saturday, 8 August 2015, Raul Piper <raulpblooper at gmail.com> wrote:
>
>> Hi Woody,
>> Form the attached datasheet section 4.3.2  the address seems to be : 0x4A
>> and 0x4B depending upon the ADDR_SEL line(low or high respectively).
>> Please check in the driver code is the address is 7 bit or 8 bit before
>> using the above address.
>> Also you can check the i2c utilities :
>> http://www.lm-sensors.org/wiki/I2CTools to check the address of the
>> devices connected with your SoC.on running i2c detect (with appropriate
>> arguments) you will come to know about the address of the devices which you
>> can verify with the address you put in the driver code.
>> Thanks and Rgds,
>> Rp
>>
>> On Sat, Aug 8, 2015 at 10:09 AM, Woody Wu <narkewoody at gmail.com> wrote:
>>
>>> I am recently porting an i2c touchscreen to my board which runs ARM
>>> linux 3.1.  I found I need to setup some device platform data for the i2c
>>> chip, among which there is an 'addr' field that I dont understand.  I
>>> search the device driver code, then I know the address will be used when
>>> compositing some i2c messages. My question is that how do I know what the
>>> address I should fill in the field? The datasheet of the device doesn't
>>> provide an answer.  By the way, the touchscreen is actually an Atmel mXT224
>>> i2c multi-touch screen panel, which is wired to a Samsung S3C i2c
>>> controller in my SoC.
>>>
>>> Thanks in advance!
>>> -woody
>>>
>>>
>>> --
>>> Sent from Gmail Mobile
>>>
>>> _______________________________________________
>>> Kernelnewbies mailing list
>>> Kernelnewbies at kernelnewbies.org
>>> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>>>
>>>
>>
>
> --
> Sent from Gmail Mobile
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20150810/4f909fdb/attachment.html