Hi ADI Engineers!
W 0x2680 to 0x4B, R back to verify: 0x2680
W 0x0001 to 0x01, R : 0x0001 : Prog mode
W 0x303A to 0x23, R: 0x303A
W 0x0A20 to 0x30, R: 0x0A20
W 0x0826 to 0x31, R: 0x0826
W 0x5AFC to 0x39, R: 0x5AFC
W 0x0001 to 0x5F, R: 0x0001 : turning on the 32MHz clock
W 0x0020 to 0x50, R 0x0020 : starting 32MHz clock calibration
Then Read 0x0A. got 0x052D (==1325) --> 32MHz clock running
W 0x0000 to 0x5F, R: 0x0000 : turning off 32MHz clock
W 0x00E07 to 0x0B, R: 0x0E07 : sending pulses to GPIO
W 0x0002 to 0x10, R: 0x0002 : jumping to run mode
Checked GPIO0, GPIO1, and LED's circuit on oscilloscope: still NO pulses ---> 32MHz running????
Mistakes in my Regs settings or a bad Eval board?
I connected the ADPD1080 Eval board to my ESP-32 WRover to work with, (on ESP-IDF/Eclipse.) The ESP-32 board has working BLE, COM, WebSocket and CAN bus to bridge PC to EFI devices. Now I'm trying to add I2S interface for the ADPD1080 and get stuck. I could write then read back registers' values while programming them, but could not send out any pulses to the IR LEDs' as expected. What were wrong. I set wrong values for regs, missed some settings, or set pulse rate to high, or worst case, the ADPD board was bad?
Should I first get and try an AD controller board instead of using my own one? The problem is I don't know if I will have control/access on the code of the AD controller board?
Thanks for every Idea.
Back to work on this project this week June 7th, 2021 with more info.
[edited by: Knguyen at 7:58 PM (GMT -4) on 8 Jun 2021]