great works

[monk31]

hello,

great works !
i use also lattice fpga but machx02 family.
At the first time, i try to upload bitstream file to spi flash with a esp8266 and here's my result
of test

1. Lattice diamond uses deployment tool to convert jed onto svf file. If you don't select
   rev D jtag , the command LOOP are not compatible and generate a error
2. I use Rev D jtag svf and i just try erase flash program in my
   bitstream.txt

, and after upload, esp8266 generate a error

log_error.txt

i only connect pin jtag on my nodemcu (esp-12e)
#define TCK 14 // NodeMCU D5
#define TMS 5 // NodeMCU D1
#define TDI 13 // NodeMCU D7
#define TDO 12 // NodeMCU D6

if you have an idea of this problem ?

best regards

[emard]

I'd say esp8266 is too sensitive to latency which can't be avoided at doing JTAG try to shorten SVF commands by 8K bits max per svf command and thats all you can do now ESP32 being a newer design, has addressed this issue and handles latency more stable than ESP8266 so I'd really recommend ESP32 over ESP8266 when I designed board ESP32 costed 30$ but now its 3$ so price is negligible

…

On 4/28/19, monk31 ***@***.***> wrote: hello, great works ! i use also lattice fpga but machx02 family. At the first time, i try to upload bitstream file to spi flash with a esp8266 and here's my result of test 1. Lattice diamond uses deployment tool to convert jed onto svf file. If you don't select rev D jtag , the command LOOP are not compatible and generate a error 2. I use Rev D jtag svf and i just try erase flash program in my [bitstream.txt](https://github.com/emard/LibXSVF-ESP/files/3124945/bitstream.txt) , and after upload, esp8266 generate a error [log_error.txt](https://github.com/emard/LibXSVF-ESP/files/3124950/log_error.txt) i only connect pin jtag on my nodemcu (esp-12e) #define TCK 14 // NodeMCU D5 #define TMS 5 // NodeMCU D1 #define TDI 13 // NodeMCU D7 #define TDO 12 // NodeMCU D6 if you have an idea of this problem ? best regards -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: #5