SX52 programmer dll & header files
jaani
Posts: 1
Hello,
I am developing a GUI in VC++ for automizing incircuit programming of a h/w board which consists of some FPGAs & SX52BD microcontroller.
How can I call SX52BD microcontroller programming from my VC++ program?
Is there any dll file & header file available, whose functions, I can call from my VC++ program?
I am using SX-key for programming these microcontrollers.
I would be really grateful to you if you can suppy me the same.
Thanking you,
regards,
mysticlol
I am developing a GUI in VC++ for automizing incircuit programming of a h/w board which consists of some FPGAs & SX52BD microcontroller.
How can I call SX52BD microcontroller programming from my VC++ program?
Is there any dll file & header file available, whose functions, I can call from my VC++ program?
I am using SX-key for programming these microcontrollers.
I would be really grateful to you if you can suppy me the same.
Thanking you,
regards,
mysticlol
Comments
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
-DAn
As mentioned, you can get the specs on the Parallax website (I can't remember exactly where) for the programming but not the debugging protocol. Still, this will entail a fair bit of work to create a working system since you are basically re-inventing the SX-Blitz wheel. One alternative which is not yet available is that there is an upgrade in the works to the SX-Key IDE (not yet available) that will allow you to call the SX-Key IDE from a command line to do things like program and debug. When will it be ready? Not sure, since there are a couple of other issues that need to be worked out before it can be released.
Just to be clear, there is NOT an official date for release of the new version of the IDE. Also, if you're thinking that having to use the whole IDE is a drag, here's a list of the command line options that will be available:
/r = Load a file as read only
/h = Hide the GUI
/b = Program using files from ByteCraft compiler
/v = Verify after programming
/p = Program the chip
/d = Debug the chip
In particular the option to hide the GUI lets your app program an SX chip without bringing up the whole GUI. You can't debug without using the SX-Key IDE, but you can program "invisibly". The command line parser makes every effort to protect the programmer from illegal combinations and does allow you to use multiple parameters such as "/r /p /v" to load a file as read only, program the chip, and then verify the chip. The order isn't critical since the parser also figure out the logical sequence of events based on what you want to do.
If you can hang in for a little while, I think this will be the best approach for your needs. If not, the Sx-Blitz protocol will let you program via the SX-Key, but the workload will land squarely on your shoulders. Of course, if you go the self programming route, you could be the cool guy who writes and releases his DLL source to the public so when the next person asks for this they won't have to reinvent your wheel.
Thanks, PeterM