hi,Chris!
I use the i2c-tools-3.0.1 tool to compile and install in DM355 EVM kernel,
For example with orders #i2cdetect 0,
prompts following information:
WARNING! This program can confuse your I2C bus, cause data loss and worse!I
will probe file /dev/i2c/0.I will probe address range 0x03-0x77.Continue? [Y/n]
Then the basis bus address range 0x03-0x07,orders the test with below:
#i2cdump 0 0x03-0x77,
only 0x5D and 0x1B two bus addresses are effective, For example # i2cdump 0 0x5d
prompt the information to be as follows:No size specified (using byte-data
access)
Error: Could not set address to 0x5d: Device or resource busy
Other bus address is invalid, For example : # i2cdump 0 0x3a
prompts the information to be as follows: No size specified (using byte-data
access) WARNING! This program can confuse your I2C bus, cause data loss and
worse!I will probe file /dev/i2c/0, address 0x3a, mode byteContinue? [Y/n]
therefore I recognize in a MT9T001.h document to define “#define
MT9T001_I2C_ADDR (0xBA >> 1)” is correct,
therefore 0x57 replaces 0xBA is not correct,
sorry for my English! thanks your reply!
winkyxiao!
> Date: Thu, 28 Aug 2008 06:42:16 -0700> From: [EMAIL PROTECTED]> To: [EMAIL
> PROTECTED]> Subject: Re: HELP ME! DM355 EVM MT9T001 question!> CC:
> [email protected]> > I've seen that problem with
> the mt9p031, or maybe the mt9t031.> > Instead of being at 0xBA it was at
> 0x57, I think.> > I used something called i2ctools (at>
> http://www.lm-sensors.org/wiki/I2CTools) to look at where everything> was
> under I2C> > good luck> Chris> > > > 2008/8/28 xiaowinky <[EMAIL
> PROTECTED]>:> > hi,ChengHao!> > I take a look at the I2C address table in
> first page of> > EVMDM355_schematics_Revd2.pdf,> > The I2C address table is
> as follows:> > 0x25 00100011B MSP430 RTC,IR CTL, IO CTL, POWER MONITOR> >
> 0x5D 01011101B TVP5146 VIDEO DECODER - 101110(I2CA)> > 0x1B 00011011B AIC33
> AUDIO CODEC - 00110(MFP1)(MFP0)> > I understood your meaning, in fact the
> MT9T001 Slave Address is 0xBA> > in write mode,> > Slave Address is 0XBB in
> read mode, in the MT9T001.h document,The address> > consists of seven bits ,
> Eighth bit position useless> > the definition to be as follows:> > #define
> MT9T001_I2C_ADDR (0xBA >> 1),> > therefore I thought is not the question
> which you said!> > Thanks your reply!> > winkyxiao!> >> >> >> >
> ________________________________> > Subject: RE: HELP ME! DM355 EVM MT9T001
> question!> > Date: Thu, 28 Aug 2008 11:38:35 +0800> > From: [EMAIL
> PROTECTED]> > To: [EMAIL PROTECTED]> >> > Hi winky,> >> >> >> > I meet this
> issue days ago,> >> > Maybe caused by the different description of I2C
> address between dm355 and> > other chipset,> >> > You can take a look at the
> I2C address table in fist page of> > EVMDM355_Schematics_RevD2.pdf, TI add
> '0' at the 8 bit and give the address,> >> > But some company adds '0' at the
> read/write bit and give an address,> >> > For example, 0011010 , in TI
> platform should use 0x1a; but some chipset spec> > give address of 0x34.> >>
> >> >> > BR> >> > Chenghao> >> > ________________________________> >> > From:
> [EMAIL PROTECTED]> > [mailto:[EMAIL PROTECTED] On Behalf Of> > xiaowinky> >
> Sent: Thursday, August 28, 2008 10:01 AM> > To: [EMAIL PROTECTED]> > Subject:
> FW: HELP ME! DM355 EVM MT9T001 question!> >> >> >> > I am trying to get the
> CCDC driver running and talking to a M9T001 image> > sensor hooked up on the
> DVEVM DM355.I have a custom pcb that adapts the> > sensor to the J30，J31
> interface using the> > same level translators that are used for the tv
> decoder chip on the board. I> > have the CAPTURE_EN pulled high to disable
> the on-board tv chip.> > I compiled the CCDC driver into the kernel as a
> static module.> > I add the following to the bootargs:> >> >
> bootargs=console=ttyS0,115200n8 noinitrd ip=dhcp root=/dev/nfs rw> >
> nfsroot=192.168.0.81:/home/xiao/workdir/filesys mem=116M> >
> v4l2_video_capture=:device=MT9T001> >> >> >> > When i boot the image I get a
> long list of failed I2C actions (shown below)> >> >> > Does anyone know what
> could cause this problem?> > Maybe it is an I2C address problem, or some
> other communication problem,> > although I see with the scope that there is
> definitely I2C data coming into> > the M9T001.> > Any help would be
> appreciated.> > Thanks,> >> > -winkyxiao> >> >> >> > i2c /dev entries driver>
> > Linux video capture interface: v1.00> > Registering platform device
> 'vpfe.1'. Parent at platform> > DaVinci I2C WARNING: i2c: AL detected> >
> DaVinci I2C WARNING: i2c: cmd complete failed: complete => > 0x0, icstr =
> 0x410> >> > DaVinci I2C WARNING: i2c: AL detected> >> > ERROR: i2c readback
> failed, val = 32, readval = 18, reg = 96> >> > ERROR: i2c readback failed,
> val = 32, readval = 16, reg = 97> >> > ERROR: i2c readback failed, val = 32,
> readval = 26, reg = 99> >> > ERROR: i2c readback failed, val = 32, readval =
> 25, reg = 100> > vpfe vpfe.1: DaVinci v4l2 capture driver V1.0 loaded> >> >>
> >> >> > -------------- next part --------------> >> >
> ________________________________> >> > MSN上小游戏，工作休闲两不误！ 马上就开始玩！> >> >
> ________________________________> >> > MSN上小游戏，工作休闲两不误！ 马上就开始玩！> >> >
> ________________________________> >> > 各位明星最近怎么样？人气榜为您奉上最新动态！ 现在就看看！> >> >
> CONFIDENTIALITY> > This e-mail message and any attachments thereto, is
> intended only for use by> > the addressee(s) named herein and may contain
> legally privileged and/or> > confidential information. If you are not the
> intended recipient of this> > e-mail message, you are hereby notified that
> any dissemination, distribution> > or copying of this e-mail message, and any
> attachments thereto, is strictly> > prohibited. If you have received this
> e-mail message in error, please> > immediately notify the sender and
> permanently delete the original and any> > copies of this email and any
> prints thereof.> > ABSENT AN EXPRESS STATEMENT TO THE CONTRARY HEREINABOVE,
> THIS E-MAIL IS NOT> > INTENDED AS A SUBSTITUTE FOR A WRITING. Notwithstanding
> the Uniform> > Electronic Transactions Act or the applicability of any other
> law of similar> > substance and effect, absent an express statement to the
> contrary> > hereinabove, this e-mail message its contents, and any
> attachments hereto> > are not intended to represent an offer or acceptance to
> enter into a> > contract and are not otherwise intended to bind the sender,
> Sanmina-SCI> > Corporation (or any of its subsidiaries), or any other person
> or entity.> >> > ________________________________> > 使用新一代 Windows Live
> Messenger 轻松交流和共享！ 立刻下载！> > _______________________________________________>
> > Davinci-linux-open-source mailing list> >
> [email protected]> >
> http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source> >> >
_________________________________________________________________
用手机MSN聊天写邮件看空间，无限沟通，分享精彩！
http://mobile.msn.com.cn/
_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
