Hello,
We have a Linux driver talking to TMS320C6412 board. We are able to read the
EEPROM content but not able to write it. If we use CSL based
PCI_EEPROMWrite/Read from DSP firmware then we are able to read and write.
So my question is can someone please tell me the eeprom write sequence and can
someone please provide the sample eeprom write sequence code.
Thanks
-Yatin
_____________________________________
TMS320C6412 EEPROM WRITE SEQUENCE CODE
Started by ●April 7, 2011
Reply by ●April 8, 20112011-04-08
Yatin-
> We have a Linux driver talking to TMS320C6412 board. We are
> able to read the EEPROM content but not able to write it.
> If we use CSL based PCI_EEPROMWrite/Read from DSP firmware
> then we are able to read and write.
>
> So my question is can someone please tell me the eeprom
> write sequence and can someone please provide the sample
> eeprom write sequence code.
Which board do you have? Is this a TI board?
If there is a CSL API for EEPROM access, it would be for the PCI configuration space storage, not for DSP program or
run-time non-volatile storage. Assuming this is what you want, then there is probably an I2C method of accessing the
EEPROM, or possibly the config space contents are stored inside an FPGA. But this is board dependent, so it's
important to know which board.
-Jeff
_____________________________________
> We have a Linux driver talking to TMS320C6412 board. We are
> able to read the EEPROM content but not able to write it.
> If we use CSL based PCI_EEPROMWrite/Read from DSP firmware
> then we are able to read and write.
>
> So my question is can someone please tell me the eeprom
> write sequence and can someone please provide the sample
> eeprom write sequence code.
Which board do you have? Is this a TI board?
If there is a CSL API for EEPROM access, it would be for the PCI configuration space storage, not for DSP program or
run-time non-volatile storage. Assuming this is what you want, then there is probably an I2C method of accessing the
EEPROM, or possibly the config space contents are stored inside an FPGA. But this is board dependent, so it's
important to know which board.
-Jeff
_____________________________________
Reply by ●April 11, 20112011-04-11
Hello,
>
>We have a Linux driver talking to TMS320C6412 board. We are able to read the EEPROM content but not able to write it. If we use CSL based PCI_EEPROMWrite/Read from DSP firmware then we are able to read and write.
>
>So my question is can someone please tell me the eeprom write sequence and can someone please provide the sample eeprom write sequence code.
>
>Thanks
>
>-Yatin
>
>_____________________________________
Thanks Jeff for the quick response. We have designed our own board using TMS320C6412 and we have used the 4-wire serial EEPROM.
_____________________________________
>
>We have a Linux driver talking to TMS320C6412 board. We are able to read the EEPROM content but not able to write it. If we use CSL based PCI_EEPROMWrite/Read from DSP firmware then we are able to read and write.
>
>So my question is can someone please tell me the eeprom write sequence and can someone please provide the sample eeprom write sequence code.
>
>Thanks
>
>-Yatin
>
>_____________________________________
Thanks Jeff for the quick response. We have designed our own board using TMS320C6412 and we have used the 4-wire serial EEPROM.
_____________________________________
Reply by ●April 11, 20112011-04-11
Thanks Jeff for the quick response. We have designed our own board using
TMS320C6412 and we have used the 4-wire serial EEPROM. We are trying to
read/write configuration space as well as store few calibration data in this
EEPROM.
-Yatin
To: c...
CC: y...@hotmail.com
From: j...@signalogic.com
Date: Fri, 8 Apr 2011 09:56:25 -0500
Subject: Re: [c6x] TMS320C6412 EEPROM WRITE SEQUENCE CODE
Yatin-
> We have a Linux driver talking to TMS320C6412 board. We are
> able to read the EEPROM content but not able to write it.
> If we use CSL based PCI_EEPROMWrite/Read from DSP firmware
> then we are able to read and write.
>
> So my question is can someone please tell me the eeprom
> write sequence and can someone please provide the sample
> eeprom write sequence code.
Which board do you have? Is this a TI board?
If there is a CSL API for EEPROM access, it would be for the PCI configuration space storage, not for DSP program or
run-time non-volatile storage. Assuming this is what you want, then there is probably an I2C method of accessing the
EEPROM, or possibly the config space contents are stored inside an FPGA. But this is board dependent, so it's
important to know which board.
-Jeff
-Yatin
To: c...
CC: y...@hotmail.com
From: j...@signalogic.com
Date: Fri, 8 Apr 2011 09:56:25 -0500
Subject: Re: [c6x] TMS320C6412 EEPROM WRITE SEQUENCE CODE
Yatin-
> We have a Linux driver talking to TMS320C6412 board. We are
> able to read the EEPROM content but not able to write it.
> If we use CSL based PCI_EEPROMWrite/Read from DSP firmware
> then we are able to read and write.
>
> So my question is can someone please tell me the eeprom
> write sequence and can someone please provide the sample
> eeprom write sequence code.
Which board do you have? Is this a TI board?
If there is a CSL API for EEPROM access, it would be for the PCI configuration space storage, not for DSP program or
run-time non-volatile storage. Assuming this is what you want, then there is probably an I2C method of accessing the
EEPROM, or possibly the config space contents are stored inside an FPGA. But this is board dependent, so it's
important to know which board.
-Jeff
Reply by ●April 12, 20112011-04-12
Yatin-
> Thanks Jeff for the quick response. We have designed our
> own board using TMS320C6412 and we have used the 4-wire
> serial EEPROM. We are trying to read/write configuration
> space as well as store few calibration data in this EEPROM.
If you designed your own board, why don't you know the write sequence for the PCI config EEPROM? How did you program
the EEPROM in the first place? Without correct PCI config the host won't recognize your board at boot-time.
Typically a board has some way to independently program the PCI config info; i.e. when it's not plugged into a PCI
slot. That could be a JTAG connection to the EEPROM, an external I2C access method (for example RS-232 to I2C
converter), etc.
Assuming you can access the EEPROM from the C6412 via I2C, then your Linux driver could send a command to its
counterpart in DSP code which would make the EEPROM write. But I'm not sure why you want to do this after boot and
after the board's PCI interface has already been enumerated.
-Jeff
> To: c...
> CC: y...@hotmail.com
> From: j...@signalogic.com
> Date: Fri, 8 Apr 2011 09:56:25 -0500
> Subject: Re: [c6x] TMS320C6412 EEPROM WRITE SEQUENCE CODE
>
> Yatin-
>
>> We have a Linux driver talking to TMS320C6412 board. We are
>
>> able to read the EEPROM content but not able to write it.
>
>> If we use CSL based PCI_EEPROMWrite/Read from DSP firmware
>
>> then we are able to read and write.
>
>>> So my question is can someone please tell me the eeprom
>
>> write sequence and can someone please provide the sample
>
>> eeprom write sequence code.
>
> Which board do you have? Is this a TI board?
>
> If there is a CSL API for EEPROM access, it would be for the PCI configuration space storage, not for DSP program or
>
> run-time non-volatile storage. Assuming this is what you want, then there is probably an I2C method of accessing the
>
> EEPROM, or possibly the config space contents are stored inside an FPGA. But this is board dependent, so it's
>
> important to know which board.
>
> -Jeff
>
_____________________________________
> Thanks Jeff for the quick response. We have designed our
> own board using TMS320C6412 and we have used the 4-wire
> serial EEPROM. We are trying to read/write configuration
> space as well as store few calibration data in this EEPROM.
If you designed your own board, why don't you know the write sequence for the PCI config EEPROM? How did you program
the EEPROM in the first place? Without correct PCI config the host won't recognize your board at boot-time.
Typically a board has some way to independently program the PCI config info; i.e. when it's not plugged into a PCI
slot. That could be a JTAG connection to the EEPROM, an external I2C access method (for example RS-232 to I2C
converter), etc.
Assuming you can access the EEPROM from the C6412 via I2C, then your Linux driver could send a command to its
counterpart in DSP code which would make the EEPROM write. But I'm not sure why you want to do this after boot and
after the board's PCI interface has already been enumerated.
-Jeff
> To: c...
> CC: y...@hotmail.com
> From: j...@signalogic.com
> Date: Fri, 8 Apr 2011 09:56:25 -0500
> Subject: Re: [c6x] TMS320C6412 EEPROM WRITE SEQUENCE CODE
>
> Yatin-
>
>> We have a Linux driver talking to TMS320C6412 board. We are
>
>> able to read the EEPROM content but not able to write it.
>
>> If we use CSL based PCI_EEPROMWrite/Read from DSP firmware
>
>> then we are able to read and write.
>
>>> So my question is can someone please tell me the eeprom
>
>> write sequence and can someone please provide the sample
>
>> eeprom write sequence code.
>
> Which board do you have? Is this a TI board?
>
> If there is a CSL API for EEPROM access, it would be for the PCI configuration space storage, not for DSP program or
>
> run-time non-volatile storage. Assuming this is what you want, then there is probably an I2C method of accessing the
>
> EEPROM, or possibly the config space contents are stored inside an FPGA. But this is board dependent, so it's
>
> important to know which board.
>
> -Jeff
>
_____________________________________
