Thank you for notifying us with the data. Appreciated.
I did some stuff with BYT-I and BYT-M. I would expect, if you run FSP on
BYT-I Stepping D0, to see for CPUID 0x30679, and for MCU to see 0x901,
0x903 and maybe more. If you run BYT-M Stepping C0, to see for CPUID
0x30678 and MCU 0x322, 0x324 or 0x325 (if I recall correctly).
If you see for BSW MCU 0x0, something is fishy. You do not have either any
MCU to update with, or the new one (which you probably collected from the
*Intel® Pentium® and Celeron® Processor N3000 Product Families and Intel®
Atom™ x5-Z8300 Processor *(formerly Braswell, Compliant with FSP v1.1
- Windows* release version 001 >
- Linux* release version 001 >
- Release notes >
- Readme >
...is somehow not reachable by Coreboot/Romstage.
So, I have here the following questions:
 Does Coreboot has FSP 1.1 spec. implemented for BSW already (5 APIs
calls, not 3)?
 Dids you download the latest BSW MCU (for which BSW), and how big the
latest BSW MCU update is?
===> Please, look into:
And pay attention to the following:
Just trying to help.
Please, Werner (Zeh), any other clues you (maybe) have for Alex?
On Fri, Apr 29, 2016 at 11:54 AM, Alexander Böcken <
read_microcode_rev() returns 0,
msr.lo is 0xFFE68430,
msr.hi is 0
These values are all good, as far as I can tell.
However, I had to dump these as post codes, because printk is not
available in this early stage in bootblock.