Yes, in case of RevealDeb the JTAG device is "soft" and created by a chunk of verilog source added to your design
How would that help me if I am not even able to transmit my own design to the FPGA?
d) what is the board's current consumption (no clock applied) in the 5V rail?
9.34 mA
I'm not surprised. I guess the MachXO2 1200 should only draw its static current when blank, which is claimed to be 3.49 mA for the 1200HC (see datasheet). (The ZE series have much lower static current.)
Add to that the relatively high quiescent current of the AMS1117 regulator. 9.34 mA sounds about right.
Add to that the relatively high quiescent current of the AMS1117 regulator. 9.34 mA sounds about right.
I am using a HT7133 which is much more low-power than the AMS1117.
Add to that the relatively high quiescent current of the AMS1117 regulator. 9.34 mA sounds about right.
I am using a HT7133 which is much more low-power than the AMS1117.
Oh, right. I missed that.
Then its 20 mA min - 30 mA typ. max output current seems on the low side though. A 1200HC will typically draw 18.8 mA during programming (see datasheet).
It also has a
peak start-up current that may exceed your regulator's capability. The datasheet suggests to use Diamond's power calculator to estimate it. I just checked on one of my designs (with a 7000HE) and it gives 68 mA for VCC and 15 mA for VCCIO!
(Additionally, if you targeted such low power, you should have chosen the 1200ZE instead...)
The highish average current you're measuring may indicate that the MachXO2 is caught in an endless start-up loop (desperately trying to start up). Looking at VCC on an oscilloscope may help check whether it's really a power supply issue.
Can you try powering it from an external voltage source?
Can you try powering it from an external voltage source?
I tried the 3.3V output from a typical USB/UART converter (CH430). It does not have a voltage regulator on it (at least I can't see it) so I guess voltage dividers are used. The limit should be the USB power limitation (which is at least 500mA).
Looking at VCC on an oscilloscope may help check whether it's really a power supply issue.
Good idea - I will try that.
Can you try powering it from an external voltage source?
I tried the 3.3V output from a typical USB/UART converter (CH430). It does not have a voltage regulator on it (at least I can't see it) so I guess voltage dividers are used. The limit should be the USB power limitation (which is at least 500mA).
It's most likely the 3.3V internal reference of the CH340, which probably has a VERY limited max output current.
Of course CH340 cannot be used for powering the fpga board, as its capability is comparable with the regulator he used before. I indicated above 100mA for the fpga only is a minimum.
OP has to wire his spare 1117 and try with that.
The 9.5mA seems to be still too much for a 3.5mA idle fpga and a low power regulator with ~uA quiescent current (no load). We discussed this topic earlier, OP has to replace the regulator and measure again.
A friend of mine has issued a ticket re FT232H and MachX02, as he plans some activity with the combo. We will see what Lat. support says. Again, Lattice KB explicitly states the JTAG signals must have pullup and pulldowns (also discussed earlier). Interestingly, the L. programming guide says the Mach's JTAG (except TCK) has got internal pullups.
A pity we do not have a regular Mach user with FT232H around who may help with testing..
OP has to wire his spare 1117 and try with that.
As I already said - the pinout of a AMS1117 and a HT7133 are not equal (Vin and Vout are reversed). But I will try to power my PCB with an adjustable power supply.
Lattice KB explicitly states the JTAG signals must have pullup and pulldowns (also discussed earlier). Interestingly, the L. programming guide says the Mach's JTAG (except TCK) has got internal pullups.
The "MachXOJTAGProgrammingandConfigurationUsersGuide" only explicitly mentions a pulldown for TCK but no pullups for the other JTAG pins.
Thank you very much for being so patient with me!
Edit: Now I see why TDO is on an all time high level - it is the output pin for data the FPGA transmits to the FT232H board.
As I already said - the pinout of a AMS1117 and a HT7133 are not equal (Vin and Vout are reversed).
For the experimental purposes you may consider to solder provisorisch the 1117 in with help of a short piece of wire
A pity we do not have a regular Mach user with FT232H around who may help with testing..
Ive got a machxo2 breakout board, it has the ftdi chip on it but 7000HE.
What would you like tested?
@DavidCh: It must be FT232H..
I powered the board with 3.3V from a DC power supply and it also didn't work
A friend of mine has got the answer from the Lat. tech. supp.:
..Theoretically, it should work if it can meet the MachXO2 hardware requirements..
..Please refer to TN1208 (MachXO2 Hardware Checklist) and the manufacturer datasheet of FT232H for more info..
In the TN1208 p.2:
Note: Erased device have all programming and configuration ports enabled by default. When the device is erase[d?] ensure SN and ProgramN are not driven low.
If I were you I would put a pullup on the SN and ProgramN (pullups always against +3.3V) and I'd try again. The checklist in the TN1208 states "external pullups" on the ProgramN and SN (as well as a 4k7 "external pulldown" on the TCK) see the Table 2.
Another hint: after you connect the FTDI in the Diomond Programmer (while wired to Mach), reset the Mach (power off/on of the Mach only) before you start the programming process.
PS: are your capacitor's values ok?