I am using a Si5341 on my FPGA board. Initially, I had not programmed the NVM on the Si5341 and was using the Linux driver to configure it dynamically. This was working fine. Now, I programmed the NVM with a default setting I would like to have, and the driver can later change this if required. However, after programming the NVM, I see the clock outputs are fine, but the driver is not able to access the chip over I2C any more. I get the error: "Failed to read chip ID". If I try to manually access the I2C from userspace, I get "No such device" error. Is this expected behavior by any chance? Does the IC become inaccessible after NVM programming?...I would hope not!
The weirdest thing is that if I connect the CB Programmer, it continues to recognize the device over I2C at the same address. However, sometimes it has now started throwing I2C errors too. Any ideas what might be wrong here?
The chip can be accessed through I2C or SPI interface after burned.
If you already checked the I2C address, then you may need to double check the SDIO and SCLK signals.
Hello...I am experiencing difficulty getting my LMK03328 to put out the tickers on its yields. I am ready to program the gadget from the default mode and get the ideal yields after the principal programming of the registers, however after I submitted these equivalent registers to EEPROM, the yields presently don't show up and I can't get the yields to empower once more. As such, I can't get another register write to yield the tickers despite the fact that those equivalent register composes effectively worked previously. I can see that the EEPROM writing computer programs is fruitful by checking the programming counter register. Does anybody know where to begin troubleshooting this?
Hi Elvis Black,
You are having problem with LMK03328 device?
If so, you can use Si5332 to replace LMK03328.
Si5332 can support PCIe Gen1/2/3/4 and have is very low jitter clock generator.
Let me know if you have any questions.