<mrec>
I'm just certain that I have flashed those ICs before with Linux. Unfortunately I don't remember how :-)
<mrec>
for sure it was not flashrom
<mrec>
when I flashed it with something existing back then I was able to break some of those ICs completely; I just don't know if it was the flash tool or the ICs were really dead (they were on a shelf for 7 years). And new ICs don't work reliable either
<mrec>
not reliable / not at all.
<olerem>
mrec: with linux i would take some SBC (RPi?) attach GPIOs or real controller to the ICs
<olerem>
or investigate why flashrom fails to do things. Whak kind of ICs do you use?
<mrec>
it's some Winbond IC. I have written some USB to SPI firmware for the stm32f0 many years ago and wrote my own flash tool which worked reliably; I will just reuse that one.
<olerem>
ok
<mrec>
back then I remember flashrom did not work properly either.
<mrec>
flashrom just states that the support is experimental (still it seems)
<mrec>
I think it's w25q64FV
<olerem>
seems to be supported by linux drivers/mtd/spi-nor/winbond.c driver
<mrec>
still need to check that part... I want the single erase function.
<mrec>
Verifying flash... FAILED at 0x00000000! Expected=0x00, Found=0xff, failed byte count from 0x00000000-0x003fffff: 0x3fe817
<mrec>
Your flash chip is in an unknown state.
<mrec>
Please report this to the mailing list at flashrom@flashrom.org or
<PaulFertser>
Why do you want the single erase function?..
<mrec>
I used another tool for flashing in the past which worked properly, I thought it was openocd
<PaulFertser>
No, flashrom is the tool that works properly. OpenOCD never supported bare flash without a target.
<mrec>
to initially clear the entire flash, I think it's required but not sure (last time I used that was years ago)
<mrec>
I always had issues with flashrom
<mrec>
that's what I know for sure
<mrec>
well I'll report back tomorrow when I'll continue with it.
<mrec>
I should be able to get it work since the correct ID was reported the rest I can check with the oscilloscope in the worst case
<PaulFertser>
It's not required.
<PaulFertser>
Yeah, I never had issues with flashrom...
<mrec>
it can easily be the ftdi combo
<mrec>
30mhz hmm...
<Haohmaru>
30MHz is quite fast, how big is that harddisk ;P~
<mrec>
flash 4mb/32mbit
<Haohmaru>
slow your horses then, drink a coffee ;P~
<mrec>
30mhz is not much even for short wires, I used short wires up to 90mhz already
<Haohmaru>
the poor little electrons :~(
<PaulFertser>
30 MHz is too damn fast
<mrec>
but ya depends on the ftdi how he's driving it I don't know this chinese board and just use the pinouts.
<mrec>
nah 30mhz isn't fast.
<Haohmaru>
it's faster than a pic12f
<mrec>
that's a baby IC
<PaulFertser>
It's not fast if you use proper cable where every second line is connected to ground and where you have at least series termination on each signal line etc.
<PaulFertser>
If you just connected a bunch of jumper wires then it's too fast certainly. Especially without termination.
<Haohmaru>
coat-hanger-grade connection
<PaulFertser>
If you say 30 MHz is fine show oscilloscope captures mrec .
zjason has joined #openocd
<Haohmaru>
<noisy_sine_waves.jpg>
Haohmaru has quit [Quit: saionara]
<mrec>
well I tested it at 7mhz no go either same unreliable as with 30mhz I think my stm32 solution was at around that speed too
<mrec>
ok I give up on that and go back to my stm32f0 flashrom is dangerous and completely breaks the winbond parts
Hawk777 has joined #openocd
<PaulFertser>
I disagree, flashrom never breaks winbond parts.
<mrec>
oh it did got a couple of dead chips here
<mrec>
well with the ftdi it certainly doesn't work ...
nerozero has quit [Ping timeout: 265 seconds]
Foxyloxy has quit [Read error: Connection reset by peer]