Other Parts Discussed in Thread: DLPA2005, , TIDA-00325
Recently we developed our own board to utilize the DLPC3435 and DLPA2005 chips, to work with a Raspberry PI CM4.
This prototype board is nearly a 1:1 match of the example schematic for the TIDA-00325 (https://www.ti.com/lit/pdf/tidrbl3)
After some debugging and small revisions, we managed to get the first board to operate properly, and works well with the PI. Some revisions that were needed, include removing some unnecessary ferrite beads, and removing two resistors on SPI which were pulling to ground on CLK and MISO.
Programming each board has been possible, and validated, using the stock firmware (I have not looked into custom firmware yet). The Boot up procedure also seems valid for each board with HOST_IRQ going high during boot, then low to signal completion, as well as RESETZ going high during the boot process. Each prototype will turn on and display the default checkerboard pattern.
However, for every board except for our first, the i2C is not responding from the DLPC3435 when probed.
I have specific questions that might help me address why this is happening and solve the problem.
1a) Does having the checkerboard pattern display, validate that the firmware is properly flashed, and that the system has booted properly?
1b) Is the Checkerboard pattern generated by the firmware on the Flash? Or is it generated by the hardware?
2) Aside from firmware, are there any reasons i2C would not initialize?
As a somewhat related secondary question
3) Is there source code I can change, or ways to customize the firmware outside of just uploading our own flash images?
Any help would be greatly appreciated. Thank you.