<whitequark[m]>
I'm really happy to have finally pushed this to completion, it's taken over 2 months when I thought it'd be one (there were a few Amaranth issues to take care of) but I'm very excited to finally have full speed flash reads
<whitequark[m]>
the QSPI mode support is a matter of implementing the right commands via a flag somewhere, it's tested already but not exposed in the CLI
<whitequark[m]>
* the QSPI mode support is a matter of implementing the right commands in the `memory-25x` applet via a flag somewhere, it's tested already in the `qspi-controller` applet but not exposed in the `memory-25x` CLI or Python interface
jstein has joined #glasgow
jstein has quit [Ping timeout: 245 seconds]
redstarcomrade has quit [Read error: Connection reset by peer]
sam_w has quit [Ping timeout: 260 seconds]
_alice has quit [Ping timeout: 260 seconds]
sam_w has joined #glasgow
yuriks has quit [Ping timeout: 260 seconds]
ar-jan has quit [Ping timeout: 260 seconds]
jdek has quit [Ping timeout: 260 seconds]
ar-jan has joined #glasgow
yuriks has joined #glasgow
jdek has joined #glasgow
_alice has joined #glasgow
<eigenform[m]>
i realized my mistake yesterday: you need to erase sectors before programming! 😐
<whitequark[m]>
oh, right
<whitequark[m]>
there's an `erase-program` command IIRC?
<whitequark[m]>
we should probably have like, high-level read and write commands that just work, and also low-level commands that give you access to individual opcodes
<whitequark[m]>
memory-25x is one of the oldest applets and that shows
<eigenform[m]>
there is! i might have tried that once, mightve been what convinced me that it was working on some blocks but not others (or something)
<js[m]>
<wklaebe> "Now I am curious what technology..." <- LoongArch CPUs :)