<ysionneau>
I am guessing the issue is my cmdline :)
<ysionneau>
bitstream contains correct idcode .. and openFPGAloader detects correct (and same!) idCode on the jtag chain ... but still somehow it's not happy ^^
<ysionneau>
I've tried with openFPGALoader v0.12.0 and v0.13.1
<trabucayre>
which cable you uses?
<ysionneau>
-c ft232 (real cable is ftdi C232HM-DDHSL-0)
<ysionneau>
I have not plugged the VCC red wire but I guess it's ok, since the board is already powered-on from some other source
<trabucayre>
Weird: look like something is wrong with idCode instruction
<trabucayre>
looks like tdi is noisy
<trabucayre>
if the device is detected this mean TCK/TMS looks fine
<ysionneau>
maybe I can reduce the clock or something
<trabucayre>
comparison is done between idcode read from the bitstream and idcode received after IR/DR transaction
<trabucayre>
could you try without --index-chain and --fpga-part
<trabucayre>
but yes maybe reducing rate
<trabucayre>
have you another cable to test? (digilent_hs2 or something like that)
<ysionneau>
with just -v -c ft232 top.bit it's the same issue
<ysionneau>
hmm no other cable I'm afraid
<ysionneau>
isn't it weird that --detect works?
<ysionneau>
isn't it using the same wires ?
<trabucayre>
detect is just a sequence of 0xff
<trabucayre>
FPGA is moved to TEST LOGIC RESET state -> SHIFT_DR followed by a long sequence of 0xff
<ysionneau>
ah so there are 2 ways of getting the idCode
<ysionneau>
what makes you say this from the output?
<trabucayre>
I'm confident about lattice code because I have used it this week to test some PoC on new cable driver
<trabucayre>
BSE Error Code
<trabucayre>
Looks some data/bits corruptions
<trabucayre>
unfortunately I haven't this cable to check is everything is fine with this cable
<trabucayre>
But usually when a cable works sometime, or with a external help (oscilloscope/LA) it's usually an issue with pull resistors or poor contact
<ysionneau>
lemme check if I forgot the pull up
<ysionneau>
I've put a pull up on TDI towards 3.3V
<ysionneau>
my bom says 4k7
<ysionneau>
maybe the assembled one is wrong
<ysionneau>
multimeter says between 4.43 k and 4.6k
<ysionneau>
trabucayre: which cable do you recommend ?
<trabucayre>
one I uses the most is the digilent_hs2
<trabucayre>
maybe Maximum output of 250mA is not enough ?
<ysionneau>
hmm if you're quoting the ft232 cable datasheet
<ysionneau>
I think it's about the Vcc wire
<ysionneau>
which I didn't plug
<ysionneau>
I could try to plug it
<trabucayre>
no
<trabucayre>
vcc from your board is usually to feed FTDI VIO
<trabucayre>
gnd is enough
<trabucayre>
but in datasheet it's Io is 250mA
<trabucayre>
Maybe I have to get one to see
<ysionneau>
ah yes right
<trabucayre>
do you have a simple ftdi break board?
<ysionneau>
nop :/
<trabucayre>
a cable not based on ftdi?
<trabucayre>
USB Blaster?
<trabucayre>
rpi2040 with dirtyJTAG?
<trabucayre>
(it's just to test with a different cable)
<ysionneau>
not sure I have another cable
<ysionneau>
but I'll check
<trabucayre>
'k
<trabucayre>
sorry I have to move a bit...
<ysionneau>
maybe some digilent cable since Ihave some digilent boards
<ysionneau>
thanks a lot for your help!
<ysionneau>
talk to you later :)
<trabucayre>
maybe yes
<trabucayre>
any cable support by openFPGALoader will be ok
<trabucayre>
an FT232RL too (but it's really slow)
<trabucayre>
or an raspberryPI with libgpiod (it's really really slow too)