Part Number: LMK03328
Hi allWould you mind if we ask LMK03328?Could you refer to the following .tcs file which is produced by TICSPRO? ■20210112_PRI=NC__SEC=TCXO27MHz___148.5MHzOUT_300MHzOUT_400MHzOUT.tcs■20210112_PRI=NC__SEC=TCXO27MHz___148.5MHzOUT_300MHzOUT_400MHzOUT.tcsOur customer uses these register data for EEPROM page 0 write.However, our customer told us that using these register data, it is impossible to use I2C.So, we persuaded to use except EEPROM page 0 like as dafault setting. In spite of page setting, they could not access using I2C.We can't belive it, however we would like to try it.We would like to try it using LMK03328 EVM.However we don't have it now.That's why, could you try it using your LMK03328 EVM?
As the point of confirmation;
1. Write all registers to EVM with this .tcs file.2. Program EEPROM on Page 0.3. Cycle Power off and On.4. After that, could you confirm whether it is impossible to access registers using I2C or not? And then, possibly check if LMK03328 output clock when it receives 27MHz clock on SecRef.
Kind regards,Hirotaka Matsumoto
We can try it on the bench but that may take a while.
In the meantime, the scan I2C bus doesn't return anything? Before programming EEPROM they could communicate with the chip but post program and powercycle they lost ability?
Can they change to ROM mode and boot up? Can they scan I2C bus and communicate then?
Thanks and regards,
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to Amin Eshraghi:
Amin sanThank you so much for your prompt reply!OK, we are waiting for your test result!
In the meantime, the scan I2C bus doesn't return anything?->Yes, your recognition is correct.Before programming EEPROM they could communicate with the chip but post program and powercycle they lost ability? ->We heard that Before programming EEPROM they could communicate with the chip. After programming EEPROM, they couldn't access registers using I2C.
Can they change to ROM mode and boot up? Can they scan I2C bus and communicate then? ->Their board is HW_SW_CTRL=GND fixed, it means that they can't modify it. We persuade to try it, however it couldn't because of board layout.Kind regards,Hirotaka Matsumoto
In reply to Hirotaka Matsumoto:
Another question did they use their own software/interface to program the factory units or is the issue occurring when they're using the EVM?
And now re-reading the original post, am I understanding correctly that the actual settings of EEPROM page 0 is irrelevant? Whether it's original configuration or customer reconfigured configuration - when in page 0, they cannot access I2C?
Can they access I2C on other EEPROM pages?
Amin sanThank you for your prompt reply!Another question did they use their own software/interface to program the factory units or is the issue occurring when they're using the EVM? ->Using TICRPRO with their board(not LMK03328EVM). And now re-reading the original post, am I understanding correctly that the actual settings of EEPROM page 0 is irrelevant?->We could not judge whether EEPROM page 0 is irrelevant or not. In our opinion, we would like to proof there is irrelevant for EEPROM writing using LMK03328 EVM.Whether it's original configuration or customer reconfigured configuration - when in page 0, they cannot access I2C?->After EEPROM writing, they recognized that they could not use I2C. Can they access I2C on other EEPROM pages? ->They tried default setting(GPIO3=GPIO2=VIM), however they couldn't access registers using I2C. So, should they confirm with other EEPROM pages?As our goal, we would like to proof there is irrelevant for EEPROM writing using LMK03328 EVM finally.
Hi Hirotaka san,
Can they boot up in ROM mode, really any of the ROM pages and see if they can scan I2C bus?
Amin sanThank you for your cooperation.We will encourage it to the customer.Kind regards,Hirotaka Matsumoto
Okay let me know how it goes. If we get to test it on the bench, we'll give an update as well.
Testing on the bench using EVM has completed. There were no issues observed - programmed page 0 using .tcs file, power cycled, I2C was still accessible. This does not seem to be related to GUI or TI silicon... they're somehow updating EEPROM byte 11 and changing the address.
Amin sanThank you so much for your great cooperation!!Ok, we got it!Kind regards,Hirotaka Matsumoto
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.