Reply #671 gives a link to a user manual for the FY6600 but that manual is V2.2 from July, 2017 and the FeelTech home page has what appears to be the latest v2.9 from August, 2017. The date on the download link for the FY6600 English manual says 2017-10-17.
http://en.feeltech.net/index.php?case=archive&act=list&catid=6
Hi guys , I am also waiting for my FY 6600 .
I have found this thread shortly after I was pay for this , so ...too late .
@DerKammi did you have paid custom tax for your ? I was ordered through Banggood .
For a new control board this ready made solutions can short time or at least may help :
https://www.embedded-wizard.de/high-performance-gui-hmi-for-stm32f7-discovery.html
With the demo version you can compile a working interface that can be uploaded to STM board .
They have even a demo of a signal generator interface here :
https://www.embedded-wizard.de/files/cto_layout/img/demo/webgl/WaveformGenerator/EmWiApp.html
Or Nextion smart displays which can send commands through Serial interface
https://nextion.itead.cc/ - This has free IDE and serial communication .
Many appreciations about your great work !
Maybe you should try to get refunds on your FY6600s.
Unless I'm getting something wrong, I'm gathering that ones that are working could self destruct at any time?
Do I have this right? Does its firmware corrupt itself?
I am happy to perform whatever stepwise procedures I can on my unit, to the extent that will help out. The STM32 attack paper is interesting reading but I lack the skill to have much hope of implementing the authors' "cold boot" attack on my own.
But I would like to mention that the most obvious board to redevelop for is not some "yet another" board, but simply the panel included with the FY6600
After all, if you clear the F103, it is just as good as new, and just as much/little work to program then any other STM32 F0, F1, F7 board. All we need to do is figure out the GPIO pin to button mapping, but you would have to make such a map on a completely new board also.
So my advise/request: please do all redevelopment on a F103 with similar GPIO mapping so it fits the original.
Reply #671 gives a link to a user manual for the FY6600 but that manual is V2.2 from July, 2017 and the FeelTech home page has what appears to be the latest v2.9 from August, 2017. The date on the download link for the FY6600 English manual says 2017-10-17.
http://en.feeltech.net/index.php?case=archive&act=list&catid=6
The PC control software is now also up to v5.5 (may be worth trying the repair_sine option again?), and other documents include detailed descriptions of the PC -> Device serial communication and arbitrary waveform data transfer protocols, which might come in useful.
Some updates: I have now written the basic functions for the FPGA (register read/write, flash erase/write/read) some macro functions (waveforms read/write and resample for display), a startup function like the original one (flash test, FPGA init, Waveform loading for the FPGA), and I am able to command the FPGA from my STM32 dev board.
I have not seen any model related limitation in the FPGA: increasing to 110Mhz the frequency of a sine wave ... outputs a 110Mhz sine wave (well, not the prettiest one )
As the serial protocol is documented, I have now connected my dev board to the other ribbon cable (serial link) and am working on programming the basic serial functions so that I can use the PC Software to control the FPGA through the dev board.
We should have shortly the basic tools needed to go on with the next parallel steps, which could be:
- Working on the GUI directly on the FP (which could directly use FPGA functions already tested with the serial protocol)
- Describing remaining high level functions (like sweep done by the FP...)
- Extending internal functions Library (Modulation, sweep, input, ...)
- Extending serial protocol functions
- Working on a new PC Software
- ...
Of course we will have to choose a toolchain before. At the moment I use Keil µvision with my dev board (with STM32F10x_StdPeriph_Lib_V3.5.0) but other choices could be fine as well (arduino with STM32duino for example could also be fine and easy for upgrades). We also have to see what kind of LCD is used...
But I would like to mention that the most obvious board to redevelop for is not some "yet another" board, but simply the panel included with the FY6600
After all, if you clear the F103, it is just as good as new, and just as much/little work to program then any other STM32 F0, F1, F7 board. All we need to do is figure out the GPIO pin to button mapping, but you would have to make such a map on a completely new board also.
So my advise/request: please do all redevelopment on a F103 with similar GPIO mapping so it fits the original.Yes, and before using the FP as dev board, any STM32F103c8t6 like this one will be perfect https://fr.aliexpress.com/premium/STM32F103c8t6.html?d=y&origin=y&blanktest=0&tc=ppc&initiative_id=SB_20180205135516&isViewCP=y&catId=0
Of course we will have to choose a toolchain before. At the moment I use Keil µvision with my dev board (with STM32F10x_StdPeriph_Lib_V3.5.0) but other choices could be fine as well (arduino with STM32duino for example could also be fine and easy for upgrades). We also have to see what kind of LCD is used..
I have not seen any model related limitation in the FPGA: increasing to 110Mhz the frequency of a sine wave ... outputs a 110Mhz sine wave (well, not the prettiest one )
A bad 110MHz sine is expected off course since the 165MHz DAC, but the limit is not there. Very nice all in all.
I don't see the firmware specified anywhere when ordering one. Any way to be sure I get the latest 3.2 firmware?
Putting this in an STM32duino toolchain is a novel but interesting suggestion. But it would mean all your code so far has to be rewritten right? Painful.
Then again, it has the advantage that people can more easily make local mods, or even do a quick temp hardcode of some sort of "special signal train" by coding very fast changes directly to the FPGA. After all, everybody and their grandmother know how to slightly mod an pre-existing Arduino program.
If it works, it would make it easier for someone else to pick up should you (heaven forbid) loose interest.
I know it was talked about, but did anyone already map out all the buttons and connections of the FB?
If not, I may have a go at that, but I do not want to be doing duplicate work.
Especially the use of PA11;12; PC12;13;14;15 may be important to figure out to see if STM32duino could run on this board (with a standard bootloader)
Yet another upload alternative would be STLink on PA13/14. Are those free at least? Probably they are, I bet its how they program in the factory.
Soldering in a standard STLink header would not be a bad idea anyway. And a clone STlink is cheap enough to permanently mount one inside the device
BTW: I thought of a disadvantage to STM32duino: it may be a low threshold. But it does not have a proper debug function where we can step through the code.
If we have to integrate a STLink anyway, maybe Keil is not so bad afterall. (I say 'we' but I am not actually writing code. This is all just musings for your consideration, fremen67)
Just made the first draft, not all is in, but keys,leds and LCD (pdf).
Leds are for power and CH1,CH2 on/off
The ST-Link is on JK1 so that is the one to use in my opinion. Standard four pin ST-Link (image).
Serial to the back are on PA2 and PA3
I like the idea of using the Atollic TrueSTUDIO mentioned earlier in this topic, worth checking/trying out, its free as of the new version.