After applying the following modification to our ComE module the board fails to boot:
We get nothing on the terminal, it seems like its in some fast reset loop as I can hear the fan pulsating. I’ve tried SD and eMMC boot, the SPI flash was not programmed prior to the mod when the board was working fine.
I’m fairly confident the mod is applied correctly and we can measure a 100MHz clock on both sides of both 0R links and a 160Mhz clock on both sides of both capacitors.
I assume there is a typo in the instructions which says to move one of the 0R links to R2381 we assumed R381 was intended.
I guess its possible something got damaged during the mod, but it was done in an ESD safe lab and we have inspected the board thoroughly under our microscope and all looks well.
Is there anyway of getting more diagnostics on a failed boot beyond UART, I guess JTAG is the only option ? Is this enabled early on in boot, is the jtag interface secured somehow ?
I could try reverting the mod, but its tricky as they are very small parts placed close to the main SoC, so want to exhaust other options first. And can you ask your hardware guys to at least use 0603 parts for interchangable/configurable components like this in the future!
Have you also changed the RCW configuration to reflect the clock changes you made for SERDES 1?
Yes, SD1 was coming up as PCIe before the mod, just gen2 not gen3, I’m using 1_13_3 config (all PCIe).
Would the board fail to boot if these clocks are not present though, PCIe/Serdes is not required for initial boot, isn’t TF-A running from ROM then loading BL2/3 from SD / eMMC / SPI ?? Surely I should get something on UART ?
The service processor configures the clocks and SERDES among other things via the RCW and PBL, before any other boot stages are attempted. If this fails then boot will hang or reset before there is any output on the serial console. The RCW setup for PLLF and PLLS need to reflect how the hardware is configured.
So I’m using the 1_13_3 Serdes configuration, but it appears after making this mod you need to use the 1S_13_3 configuration, I’m not in the office today so cannot test it, but fingers crossed this will work.
I can confirm that using the 1S_13_3 configuration fixed my none booting issue, cheers!
Maybe you should add that info to the hardware wiki, along with the mod details.