I'd go for the DSLogic, but that comes from china, I do not want to wait 3 weeks. I'll look for something closer by.
I have 3. One China, and 2 more integrated into official distributor bought real ST brand STM32F0 discovery boards.
As stated, both Bluepills behave the same, both can be programmed to a simple "blink" program and work, both can be programmed to fremen's and then read back to compare without issue. One Bluepill was brand new out of silver anti-static wrapper. So I have very little doubt about the BluePill or STLink themselves.
Nevertheless, I tried once more using the STM32F0 integrated STLink, just to read back. Program verified without problem, was thus properly programmed with the China STLink, and anyway after reprogramming I had same result.
Well, almost same: When connecting both 4 and 8 pin result is the same.
But doing this, I discovered that if I only connect power (4 pin header) and not the 8 pin header, the LED does turn off, it does get past initialization.
Added my pull-up resistor again, but still not work. Something is unstable on that SPI bus when connected.
It may be because I have slightly older hardware. I need to properly spy that bus.
I'd go for the DSLogic, but that comes from china, I do not want to wait 3 weeks. I'll look for something closer by.
I am in dire need of a new/better LA
Trying to figure out why it is not working anymore. It is weird, because the BP was never disconnected from the loom, so there is not much chance of me making a mistake with it.
Tried a new BP, and soldered it to a veroboard for better signal and connection quality, and same result. Both BP have the red LED stay on, and both BP nicely run the standard "blink" program from STM32
Using my LA at max 20MHz I am not able to decode what is happening, because the SPI is also at 20Mhz. Ergo, I need a LA of at least 40MHz, better 80MHz
Using my Scope, I was able to see that the SPI signals themselves are pretty clean and well defined, but with the startup delay and limited scope trace, I am not really seeing what is happening (good thing I never paid for the decoding, it is not so very useful)
So:
- Any chance Fremen you can, without too much effort, make a custom 5Mhz clocked version?
- Anyone has advice on what LA? Spec-wise I like the ScanaQuad SQ100, but its a bit pricey and I'd maybe like 8 instead of 4 channels.
(maybe I should go and search a different thread for that, but here I am anyway)
PS: CHecked and re-checked, so pretty sure about the wiring. But if anyone wants to look, see pictures.
ALso, I keept the veroboard a little larger, so I can add buttons in the future...
Sellers on eBay and AliBaba that claim to be in UK or Germany are lying.
I know people do actually exist in UK and Germany, but only a few million, and there is like a few billion people in China, so statistically above statement is true.
Also, I noticed the eBay sellers do not include the special coax-probes, but just the straight lead probe
Picture one: Yellow is 20Vpp into 50 Ohm with THS3095
Blue is reference waveform10Vpp into High-Z. You do not even see the blue because they are so equal.
1. Power supply
Classical transformer 14Vx2/20VA
Linear regulators 14V DC for some output peak headroom - possibly LM317/337Make sure the 14V has good good buffer caps, or else make the rail 12.5V instead of 14V. Because 14Vdc from 14Vac may cause some ripple if your caps are too small.
Especially since it was reported the 3095 on 11.5V already barely had clipping, so better a stable 12.5V then a ripply 14VDC-DC to 6V and then linear to 5VNo need. That 5V is not used except to have a linear to 3.3V. So your DC-DC may as well go to 5V directlyDiode clipping to the power supply rails - BAV99Ok, I missed that one. Why/How clip to rail with BAV99? Is that still needed if you replace the entire PSU?
Will any other components besides the ferrite & new power supply be needed to power the dual THS3095 output op amps, other than a grounding cable to reference the BNC ground to mains earth?
Finally, are the THS3095's just a drop in replacement for the single output op amp or am I going to need to solder in additional components around them?
...and installing a new TXCO reference
Thanks, I needed the higher voltage supply to help handle the waveform clipping problem in the output. I just realized that I will need to put a 5V regulator after the 12v output in order to supply the necessary 5v for the rest of the board. Any suggestions for how I should manage that?
First test: Just plug the 4 wires ribbon and you should be able to talk to the board via PC Software.
If it works, second test: plug the two ribbons, except the /FPA Ready pin (you may have to de-solder one wire now with your vero board...). If it works then it comes from a different timing of this signal for whatever reason.. I could just release a FW version that continues init after a time-out. If it does not work than it might come from SPI init. I should have a look at how to recover from this one.
For this you should take a step down converter that is capable of >1A not a 5V regulator like the 7805. On the 5V rail there is up to 1A needed. Using a 7805 it would need to dissipate (14V - 5V) * 1A = 9V * 1A = 9W! You get step down converters very cheap as ready to use modules. With a small heatsink the XL4015E1 (see picture) would be a good choice. It is capable of up to 5A. This module is only about 5cm x 2,5 cm x 2,5cm.
Also, I noticed the eBay sellers do not include the special coax-probes, but just the straight lead probes.
You may have missed the message just above yours.
Forgot to press refresh I guess.
Also, I ordered the DSLogic. From original website. No mention of delivery times, so likely 2 weeks minimum. But I am gone all next week anyway.
First test: Just plug the 4 wires ribbon and you should be able to talk to the board via PC Software.confirmed: both the vero-PB and the loom-BP connect to PC software if only the 4-pin is connected.
btw: unlike what was stated before, it is the green LED that turns off after init.If it works, second test: plug the two ribbons, except the /FPA Ready pin (you may have to de-solder one wire now with your vero board...). If it works then it comes from a different timing of this signal for whatever reason.. I could just release a FW version that continues init after a time-out. If it does not work than it might come from SPI init. I should have a look at how to recover from this one.Both the vero-BP and the loom-BP do not work if I disconnect the /FPGARDY signal.
For added info, I attach a scope view of the SPI bus signals. Not sure if it helps in any way.
The first 2 are that I captured between BP and FPGA. The last 2 between FP and FPGA. While there are some overshoots on vertical edges, there is no noise, and there is a good clear difference between 0 and 1.
When BP is connected, these signals are shown over and over again. Hence the they are captured in RUN and nicely bright. My guess is the BP is trying to get the FPGA to say something, but it stays silent.
When FP is connected, the SPI is pretty much silent. I have to press a button to capture some bytes. Hence captured in SINGLE.