Hi Nico!
Thanks for explaining. :) So what can I do in this case? Which programmer
is the easiest to get the setup working? Rayer_SPI didn't even detect it,
nor with shorter wires, this is why I went to ICH7, at least it can
recognize KB9012, and read some random data from it. I will not connect
Hi Nyúlós,
On 20.01.19 12:46, Nyúlós Lónyál wrote:
> There are some programmer_delay values in ichspi.c, here is one which says
> something about frequency:
>
> timeout = 100 * 60; /* 60 ms are 9.6 million cycles at 16 MHz. */
> while ((REGREAD16(ICH7_REG_SPIS) & SPIS_SCIP) && --timeout) {
>
There are some programmer_delay values in ichspi.c, here is one which says
something about frequency:
timeout = 100 * 60; /* 60 ms are 9.6 million cycles at 16 MHz. */
while ((REGREAD16(ICH7_REG_SPIS) & SPIS_SCIP) && --timeout) {
programmer_delay(10);
So I just need to increase programmer_delay,
Maybe try inserting some extra programmer_delay(n) to your ichspi.c ?
Also I had a patch for the unreliable flashing environments -
https://review.coreboot.org/c/flashrom/+/23840 - but didn't improve it
yet so it haven't been merged, and already incompatible with the
latest flashrom. Also maybe it
Thanks for replying at my noob questions. :) The spispeed parameter, yea, I
thought about it after looking into flashrom's source on GitHub. Sadly it's
not in the code of ICH7 chipset (ichspi.c), so the spispeed option in
flashrom command is unavailable. Someone already did that for AMD SB600
Sorry for a long reply, I just watched your video and - unless you
changed its' speed - it seems to me that your KB9012 operations are
going faster than expected, e.g. it reached 0x4*** address almost
instantly while in my CH341A case it was almost certainly slower. So
maybe you could experiment
Same problem with 5cm long copper wires. Here is a video of what's
happening: https://www.youtube.com/watch?v=JlbRGK9_gPg
Nyúlós Lónyál ezt írta (időpont: 2019. jan.
16., Sze, 1:38):
> The wires are ~20-25cm made of aluminium, but I have some broken USB
> cables with copper wires. I can reduce
The wires are ~20-25cm made of aluminium, but I have some broken USB cables
with copper wires. I can reduce the distance of laptop's keyboard connector
and DIP8 socket to about 5cm wire length, will give it a try tomorrow. And
something that I've noticed at verifying with flashrom, it always gives
Sorry if I've already asked this question, but how long are your
wires? Ideally they should be about 10cm length and made of good
copper. Although it could work even for 30cm poor aluminum wires,
still when there are read/write errors - the first suggestion which
comes to my mind is to shorten the
Sorry for the confusion. :( I think you have misunderstood me.
My laptop's motherboard is taken out of the laptop. I have another machine,
a desktop PC which I've used for trying rayer_spi programmer. Now I connect
the laptop's KB9012's debug pins into the desktop PC motherboard's DIP8
BIOS
That is because KB9012 is active after your laptop has booted and not
in debug state where it is possible to reflash it without a problem.
Have you double checked your laptop's datasheet to make sure your
connection is correct, and also that your laptop's corner ground is
really connected to its'
Finally managed it to detect KBC's internal flash using the motherboard's
BIOS socket with removing it's SPI chip after boot, and connecting KB9012
in there. But the read always gives me different files, so I can't backup
the current content of KB9012.
Sorry for double mail. Erasing and writing fails too.
*xubuntu@xubuntu:~/flashrom$ sudo ./flashrom -p internal -c "KB9012 (EDI)"
-w /home/xubuntu/Desktop/EC-FD-Extract.bin flashrom p1.0-141-g9cecc7e on
Linux 4.15.0-20-generic (x86_64)flashrom is free software, get the
Yea, tried to discharge the motherboard, taken out CMOS battery too, it
didn't help. I don't know if this is programmer related or not, I have
reflashed 2 types of BIOS SPI chips with it, EN25QH16 and W25Q32BV. But
these chips are maybe different from KB9012's debug interface. I can't get
a CH341A
Hi Mike!
I've followed the linked guide, it gave me these results. The grounds are
united, still the same error happens. I have tried to GND pin 42 of KB9012
as mentioned in the guide, and tried to connect both pin 41 and 42 to GND,
as in KBC's datasheet at EDI related part, still no success,
Just to double-check: please discharge the motherboard completely by
trying to turn it on while there is no power adapter connected, then
unite three grounds (KB9012 / programmer / motherboard ) and only then
connect the board's power adapter . After doing all that, please check
if you could read
This rayer_spi is "RayeR parallel port programmer" which is external.
Internal flashing will not work until someone will reverse engineer
the proprietary UEFI update mechanism part of updating EC firmware.
P.S. Meanwhile I'm contributing various patches to coreboot,
although they are not discrete
Mike Banon wrote on 1/8/19 3:08 PM:
Hi Nyulos,
Have you tried following the KB9012 flashing instructions at
DangerousPrototypes wiki?
http://dangerousprototypes.com/docs/Flashing_KB9012_with_Bus_Pirate
Although that is for Bus Pirate / CH341A programmers and LA-A091P,
should be similar for your
Hi Nyulos,
Have you tried following the KB9012 flashing instructions at
DangerousPrototypes wiki?
http://dangerousprototypes.com/docs/Flashing_KB9012_with_Bus_Pirate
Although that is for Bus Pirate / CH341A programmers and LA-A091P,
should be similar for your Rayer programmer and LA-8241P
19 matches
Mail list logo
