1) Document number 595776 talks about flashing BIOS via J3H1.
However I haven't found RVP schemtaics/image which shows the location of this connector.
Is there such?
2) There are 2 matching connectors on the RVP. So I've tried both to detect chip using DediProg SF600 on Ubuntu 18.04 and I'm trying to detect chip with the following command "sudo dpcmd -d" but I get "Error: chip not identified."
Thank you for contacting Intel Embedded Community.
The J3H1 listed in your previous message is a location. You can find the cited jumper using the marks located in the Customer Reference Board (CRB) Printed Circuit Board (PCB), as is showed as a reference in the attached picture. This location is a kind of ordered pair, which is generally referenced to axes located in the borders of the PCB.
On the other hand, your consultations of the mentioned programmer should be addressed as a reference to the channel listed on the following website:
Attached are more pictures.
Hopefully they are good enough.
Notice that there are 2 matching connectors (I've sent a picture of both).
One connector is close to some SPI flash so maybe it is the one to use for BIOS burning but the other has SF600 printed close to it so maybe it is the one to use for BIOS burning.
Attached is a clearer image of the connector (now I can see J3H1 written close to the connector).
Still for some reason both dpcmd and flashrom are unable to detect the chip.
Am I missing something?
Is there a jumper to toggle in order to be able to detect the chip?
We are glad that you find the connector.
You should follow all steps stated in section 4.3, on pages 19 and 20 of the Whiskey Lake U Platform RVP Customer Reference Board User Guide document # 595776. You can find this document when you are logged into your Resource and Design Center (RDC) privileged account on the following website:
You should fill out the form stated on the following website when you have problems with the provided website or want to update your RDC account:
By the way, we suggest verifying that the software and its version are proper for the cited programming tool as a reference please review the information stated on the following website: