Hi,
I am trying to communicate via I2C between two devices, one of them is GreenPAK Advanced Development Platform with inserted chip SLG46826V, which supports I2C communication. What I am trying to do is send 8-bit information from one device to GreenPAK Platform via expansion connectors on PIN 8(SCL) and PIN 9(SDA). I made a fairly simply program on GreenPAK6 Designer, which communicates with other device. When I put a new chip on the Development Platform and run Emulation (sync), everything works fine, I can see on oscilloscope that those have been sent. Emulation (sync) loads any new changes made to the project, so what I tried to do is change control code, e.g. changing from control code 0000 to 0001. When I do that, program stops to work and chip is supposedly absent or not inserted. When I try to re-run emulation, I get Socket test message, which says that: "Functional socket test failed. Socket issues detected." Even when I press Skip and proceed, next error appears: "I2C tranfer fail".
Please let me know if you can help me with this and thank you in advance for any help provided.
Best regards,
Adi
Hi Adi,
Thanks for reporting this. While we are trying to reproduce the issue, could you please let us know the following information?
1. Which GreenPAK Designer version do you use?
2. Was the chip previously programmed?
3. What are the lock options of your design (Project settings->Security)?
Best regards,
Roman
Hi,
1. I use version 6.20
2. Chip was previously not programmed
3. NVM options: Lock status - unlocked with pattern ID = 1;
2k NVM Configuration: Proteck lock - disable, Protect mode - data is unprotected for read and write/erase
Emulated EEPROM Write Protection: Write protect - disable, Write protect macrocell bits - upper quarter of emulated EEPROM is write protected
Best regards,
Adi
Hello Adi,
谢谢你的评论。我是一个技术工程师responsible for GPAK. I've just talked to Roman and we are now verifying what is the reason of that issue.
It would be great if you could send the design (*.gp file) which you are using. This might help us a lot, since we could not reproduce this issue up to now.
Best regards,
Yurii
Hello Yuri,
Here is the design that I used (very simple design, but still does not work the way it is expected).
Best regards,
Adi
Hi Adi,
We are still trying to reproduce this issue. I have passed it to the software team to look at it more detailed, because on my computer and dev tool everything works fine. Does the problem occur all the time?
Best regards,
Roman
Hi Roman,
Yes, the problem occurs everytime. If I put new chip inside and start emulation, everything works fine until I try to change e.g. control code.
Best regards,
Adi
Hi Adi,
We are still trying to reproduce the fail. But we have one idea. Could you please try adding pull ups on PIN8 and PIN9 by right clicking on the (NC) next to each pin and chosing Pull Up in the context menu? Please let us know the result.
Best reagrds,
Roman
Hi Roman,
Unfortunately, the situation stays the same as before. Do you perhaps have design with I2C communication for my specific chip, that works for you? Maybe if I try your design, it will work.
Best regards,
Adi
Hi Adi,
Many thanks for the file. We will try to find out the reason and come back to you with the result as soon as possible.
Best regards,
Yurii