Purpose of the SX/C Wiki:
To serve as central repository for documentation, demos, tutorials, source code, and bug reports. Questions and communication regarding the SX/C compiler should be posted to the proper Parallax forum. I feel that the Parallax forums provide great information and help when it comes to issues and problems. If you feel that the resolution to a problem, issue, or bug warrants entry in the SX/C Wiki, then by all means, post it.
Mission of the SX/C Wiki:
The mission of the sxcwiki is to develop a better understanding, on a community level, of the SX/C compiler. To achieve this goal, the following are “core” areas that will need to be built upon and improved:
Develop demos and tutorials that are aimed toward specific audiences, such as beginners, intermediate, and experienced users. Therefore, if a demo or tutorial is developed it should be labeled for its intended audience.
Provide real world applications/projects as an example of what can be with a SX microcontroller when using SX/C.
Provide bug reports to make other users aware of what bugs may be encountered for a specific version of SX/C. Also, documentation concerning temporary circumvention of a bug would be appreciated.
Increase overall user understanding by editing/enhancing demos, tutorials, or other documentation materials.
Most important - Have fun and enjoy the experience!
Please note that the SX/C Wiki is not maintained nor affiliated with CCS, Inc. or Parallax, Inc. It is maintained by an independent user with contributions from the SX/C community. There are no guarantees of any kind concerning the content and functionality of the sxcwiki. The head maintainer can be reached at the following email address: alinious [noparse][[/noparse]at] gmail [noparse][[/noparse]dot] com or the Parallax forums.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
"I learn when I succeed, but I learn more when I fail."
I visited the sxcwiki page and noticed the SX/C version is listed as 4.042
The latest sxcupd.exe I downloaded from the CCS website changed my
beta from 4.016 to 4.044, so the people·that received a CD should
download the latest update, as some bugs may be resolved in version 4.044
I have been trying to figure out a way of getting around the SX Wizard and Create "bug". You guys can call it a "bug", I call it crippled. What I did is, using notepad, create a .c file, for instance test.c. At this point the file should have the SXC icon. Next double click on the new file, which should open up the·SXC GUI. Before you put any source code into the file, do a compile on the file. At this point it should create the necessary .prj file, and whatever else it needs. Now, if you use the Project tab, your new prj should be in the directory listing. Now you can proceed with adding the code to your source file. I just added the #include <SX28AC.H> and void main() {}, and compiled it without any errors. It only compiled, I have not·tested with a complete program to see if it actualy works or not.
I dont know if Ill be able to get to it today or not (late night if at all) but I will make sure I give my input soon on the wiki. Thanks for the tip peter, Ill make sure I get that downloaded shortly.
Ray,
Please let us know if you have any success in getting a complete operating program with your method, it is likely to be something worth putting on the wiki.
Jared
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
A wise man who is not known for sure to have existed once said, "Never test a river with both feet." I feel this is especially true in engineering...throughout history everytime something new was tried with little research or planning, the odds were stacked in favor of failure, and everyone knows the house always wins in the long run....
Well, the bad news, programming the chip is crippled. When you do the Program Chip, it goes through the motions, but it does not program the chip. I used the SX_LED.C program, just to be consistent, that did not help as far as programming the chip. I have an SX Tech board, and a couple of SX52 proto boards that I use. I have not run across this kind of crippleware in a very long time.
So, the best I could do is, use the method I described to create something new, then you can still use Debug to get the program to run. A feature that is missing is the Run, now you have two choices Debug or Program, since Program has been crippled, down to one choice.
The other problem I noticed is when I set up my LED program for my SX52 proto board, running debug would not work, error was - Reset needed at the end of memory. So, I expect to encounter a lot more problems with the SX52.
I am surprised that somebody from CCS or Parallax has not jumped in and to either confirm or deny my claim that this is major crippleware. Then we would know that the software has some major "bugs".· This is starting to feel like real hard work, I usually like to have fun with this stuff.
The error regarding the SX52 was reported on 10/25/2006 on the sx/c beta test forum.
Here are those messages:
Hi-
I have my first SX C program running (and debugable) on the SX-28; however when having first tried to run this program on an SX-52 Proto Board I ran into problems:
When starting the debugger this error came up:
"ERROR! Debug requires RESET jump at the end of memory"
Looking in the debug output COD.txt file, these appear:
I had these in the program:
// #include <SX28AC.H>
#include <SX52BD.H>
#include "atd_emu.h"
// #fuses HS,NOPROTECT,NOWDT
// #fuses NOPROTECT,IRC,NOIFBD,NOSYNC,XT2,NOWDT,OPTIONX,IRCTRIM_MAX,BORTRIM3,4PAGE_8BANK
#fuses· HS,NOPROTECT,NOSYNC,NOWDT,IRCTRIM_MAX
Just reporting a bug....
Thanks,
RW Senser
Hi-
Some additional information on this SX-52 error: This error does not occur with the SX-48 (nor with the SX-28).
I'm not sure if the SX-52 is still considered "supported"; my personal view is that it should be <smile>.
Thanks,
RW Senser
This could be because the compiler recognizes the chip as a 2 Kbytes while, it actually is a 4 Kbyte chip. The SX-28 chips has fuses to tell the compiler what size memory it has, while the SX-52 does not do that. So i dont know why this could be hapenning, but i will check to see how the compiler is configuring the device.
If you have trouble programming a chip, or the chip does not appear to run correctly,
it may well be due to incorrect fuse settings.
Here is a possible workaround that was also posted (by Chris Savage) on the sx/c beta test forum:
·· If you program the device without the PROTECT set you can read the device into the Device Screen and see the fuse options that are listed to confirm them.· If something isn’t setting right you can change it after the read and program the SX from within that window to correct that problem.· I hope this helps.· Take care.
For all those new beta testers that are not yet signed up to the sx/c beta test forum,
request to sign up to the sx/c beta test forum, as it holds vital information what has
been tested (and should have been fixed now).
Peter Verkaik said...
I visited the sxcwiki page and noticed the SX/C version is listed as 4.042
The latest sxcupd.exe I downloaded from the CCS website changed my
beta from 4.016 to 4.044, so the people that received a CD should
download the latest update, as some bugs may be resolved in version 4.044
thanks for the info about the CCS update site. Before getting access to this site, you need to register with CS first. While doing this, I was asked to enter the locations of three *.crg files. I could not find any of these on my computer. The only one I found was named sxc.crg, so I have filled in this information, hoping that this works. How did you successfully register your copy of SXC?
Hi Guenther,
I do not have a CD copy of Sx/C, but as I am a member of the sx/c beta test forum,
all I have are downloaded versions. To be able to download an update you need a registration number
and you only get that after purchasing a copy. All the sx/c beta testers that joined the
sx/c beta test forum got a fake purchase (purchase at no $$$) and so we have such
a number. I remember they sent an attachement (.crg file) to my email address
that allowed me to download.
To speed things up I am willing to post the update here, but I need
approval to do this·from Parallax or CCS. If they say I can post it, no problem.
(Any Parallax staff member·reading this?) If not, you must wait for CCS
to grant you access to·download (and this could take a long time).
Edit: the size is 15MB, so no chance posting it here.
If I get approval I could mail it directly to you (if your mailbox can accept 15MB)
Does the CD you got have no instructions how to obtain updates of the product?
If you startup the sx/c IDE, you can try Help->Check for S/W updates
Maybe it is automatically detected that you have a legal copy.
regards peter
·
Post Edited (Peter Verkaik) : 7/24/2007 11:35:15 PM GMT
As for your problems with the SX Tech board, review my previous posts and read the help file regarding direct device programmng...there is some setup that is required at which point it will work fine. I assure you this software is far from crippled if you would just give it a chance.
Jared
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
A wise man who is not known for sure to have existed once said, "Never test a river with both feet." I feel this is especially true in engineering...throughout history everytime something new was tried with little research or planning, the odds were stacked in favor of failure, and everyone knows the house always wins in the long run....
To anyone testing the CCS compiler (version 4.046 or lower), please be aware of an existing bug that can disable all the commands to talk to the SX IDE. If you add or modify any of the strings for the debug or program commands via the Options->Tools menu, you may discover that your new command doesn't work. If you close the CCS IDE and re-open it, you'll likely discover that all of the tools have been disabled.
If this happens, close the CCS IDE, go to the directory with the CCS compiler and IDE and open a text file called PCW.INI. Look for the section labeled [noparse][[/noparse]usertools] near the top. You'll see all your command line for your tools have a {{ at the head and tail of them. Using your text editor, do a search and replace, converting {{ to {. Re-start the CCS IDE and the tools should be working again. I have notified CCS of this bug and expect them to fix it soon. Just be aware that anytime you make a change to the user tools via the IDE, the IDE will disable them, and you'll have to follow this process again. It's not hard to do, just annoying.
I have attached a pair of screenshots to show the problem in the GUI. Note how in the tools dialog, all the strings have an extra quote head and tail. This is {{ from the ini file.
thank you for the information. In the meantime, CCS has sent me an eMail with the necessary download information for the update. So CCS was much faster this time than you had proposed.
Peter Verkaik said...
Hi Guenther,
I do not have a CD copy of Sx/C, but as I am a member of the sx/c beta test forum,
all I have are downloaded versions. To be able to download an update you need a registration number
and you only get that after purchasing a copy. All the sx/c beta testers that joined the
sx/c beta test forum got a fake purchase (purchase at no $$$) and so we have such
a number. I remember they sent an attachement (.crg file) to my email address
that allowed me to download.
To speed things up I am willing to post the update here, but I need
approval to do this from Parallax or CCS. If they say I can post it, no problem.
(Any Parallax staff member reading this?) If not, you must wait for CCS
to grant you access to download (and this could take a long time).
Edit: the size is 15MB, so no chance posting it here.
If I get approval I could mail it directly to you (if your mailbox can accept 15MB)
Does the CD you got have no instructions how to obtain updates of the product?
If you startup the sx/c IDE, you can try Help->Check for S/W updates
Maybe it is automatically detected that you have a legal copy.
For anyone who is testing the CCS compiler SX/C, there is a BETA version of the SX-Key IDE which should help alleviate some problems. It's BETA, so be aware that there may be some bugs, but it should be stable enough for regular use.
To use it, simply un-zip the contents into an empty directory (not the SX directory with your current SX-Key IDE) and run the program SXKey.exe. It will prompt you to let it install the SX/B compiler, etc. Let it. As long as you install this in a new directory, it won't interfere with you current SX-Key IDE installation.
The following are the bugs that it fixes (not all are SX/C specific):
1 - New COM port enumeration code to find USB serial ports more accurately
2 - Fixed bug that crashed IDE when programming via command line with GUI hidden
3 - Fixed bug that didn't close IDE when COM error occurred during command line execution
4 - Fixed bug where IRC calibration dialog didn't display. It now displays only when "Program" is invoked, not "Debug". It does the calibration during "Debug" programming, but doesn't show the dialog.
In addition, here is the list of command line switches supported by the SX-Key IDE. These are used to set up the "User Tools" in the CCS IDE so it can invoke the SX-Key IDE for things like programming. I have posted this info before, but here it is again:
/r = Load a file as read only
/h = Hide the GUI
/v = Verify after programming
/p = Program the chip for standalone operation
/d = Debug the chip
/da = Debug chip again (do not download code and assume it is the same as the editor window)
/b = Program using files from ByteCraft compiler. (Backward compatibility only. Not needed with the CCS compiler.)
The name of the source file that should loaded MUST be the LAST element on the command line.
For anyone who finds it weird that the CCS IDE doesn't keep using the same IDE over and over, it's because it really should be invoked with the -h switch to hide the editor. By doing this, it makes the SX-Key IDE feel more like a part of the CCS IDE, and it also will do things like automatically close itself after programming is finished.
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.
Please note that all commands and switches in the user tool section of the CCS IDE must have quotes before and after each one separately. Take a look at the existing user tools to see how that works. Also, please see my earlier post in this thread about the bug in the CCS IDE that forces you to edit the PFW.INI file after making changes to the user tools.
The password for extracting the ZIP file contents of the BETA 3.2.7 SX-Key IDE software is:
Parallax
I believe the password is case sensitive, so make sure to capitalize that first P.
For those wondering, "Why is it password protected?" It turns out that the Parallax email server doesn't like it when I send regular ZIP files to Ken. However, it is fine with password protected (e.g. encrypted) ZIP files. In the rush to get it up on the server, I imagine that Parallax simply forgot to re-save the file as a non-password protected ZIP file.
PeterM,
It's because the virus scanner scan for filenames within the ZIP. If there is an .EXE or .DLL it gets blocked.
If it's password protected, it cannot scan it.
Bean.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Teacher: What is the difference between ignorance and apathy ?
Student: I don't know and I don't care
Teacher: Correct !
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - www.hittconsulting.com ·
Thank you! I must concur with Bean because Gmail blocks files containing .EXE, thus, I must resort to other tactics when I need someone to send me this types of file.
-Alan
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
"I learn when I succeed, but I learn more when I fail."
Well, I just installed the BETA version, the big problem, SX-key can not be found on any com port. The non-BETA version works without any problems. As for the SXC, while using the BETA ide, nothing changed for the better, everything is still the same. Hopefully, one of these days I will get to experience the real SXC package.
I believe the phrase you are looking for is "credibility problem"
Why throw our cycles at it when they won't respond for months and years at a time? Or haven't in the past.
What bugs were fixed? What work was done? What features were added? Do the example programs actually compile and function? Does it work with the SXKey IDE?
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
---
James Newton, Host of SXList.com james at sxlist,com 1-619-652-0593 fax:1-208-279-8767
SX FAQ / Code / Tutorials / Documentation: http://www.sxlist.com Pick faster!
Comments
I have created a wiki for the SX/C compiler located here: SX/C Wiki - sxcwiki.alanbalich.com.
Purpose of the SX/C Wiki:
To serve as central repository for documentation, demos, tutorials, source code, and bug reports. Questions and communication regarding the SX/C compiler should be posted to the proper Parallax forum. I feel that the Parallax forums provide great information and help when it comes to issues and problems. If you feel that the resolution to a problem, issue, or bug warrants entry in the SX/C Wiki, then by all means, post it.
Mission of the SX/C Wiki:
The mission of the sxcwiki is to develop a better understanding, on a community level, of the SX/C compiler. To achieve this goal, the following are “core” areas that will need to be built upon and improved:
Please note that the SX/C Wiki is not maintained nor affiliated with CCS, Inc. or Parallax, Inc. It is maintained by an independent user with contributions from the SX/C community. There are no guarantees of any kind concerning the content and functionality of the sxcwiki. The head maintainer can be reached at the following email address: alinious [noparse][[/noparse]at] gmail [noparse][[/noparse]dot] com or the Parallax forums.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
"I learn when I succeed, but I learn more when I fail."
Alan Balich
SX/C Wiki - sxcwiki.alanbalich.com
Post Edited (alinious) : 7/24/2007 4:29:49 PM GMT
The latest sxcupd.exe I downloaded from the CCS website changed my
beta from 4.016 to 4.044, so the people·that received a CD should
download the latest update, as some bugs may be resolved in version 4.044
http://www.ccsinfo.com/scenixupdates.php
regards peter
Post Edited (Peter Verkaik) : 7/24/2007 6:38:58 PM GMT
I dont know if Ill be able to get to it today or not (late night if at all) but I will make sure I give my input soon on the wiki. Thanks for the tip peter, Ill make sure I get that downloaded shortly.
Ray,
Please let us know if you have any success in getting a complete operating program with your method, it is likely to be something worth putting on the wiki.
Jared
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
A wise man who is not known for sure to have existed once said, "Never test a river with both feet." I feel this is especially true in engineering...throughout history everytime something new was tried with little research or planning, the odds were stacked in favor of failure, and everyone knows the house always wins in the long run....
So, the best I could do is, use the method I described to create something new, then you can still use Debug to get the program to run. A feature that is missing is the Run, now you have two choices Debug or Program, since Program has been crippled, down to one choice.
The other problem I noticed is when I set up my LED program for my SX52 proto board, running debug would not work, error was - Reset needed at the end of memory. So, I expect to encounter a lot more problems with the SX52.
I am surprised that somebody from CCS or Parallax has not jumped in and to either confirm or deny my claim that this is major crippleware. Then we would know that the software has some major "bugs".· This is starting to feel like real hard work, I usually like to have fun with this stuff.
Ray
The error regarding the SX52 was reported on 10/25/2006 on the sx/c beta test forum.
Here are those messages:
Hi-
I have my first SX C program running (and debugable) on the SX-28; however when having first tried to run this program on an SX-52 Proto Board I ran into problems:
When starting the debugger this error came up:
"ERROR! Debug requires RESET jump at the end of memory"
Looking in the debug output COD.txt file, these appear:
Memory Map
········ Start···· End
·· 0:···· 0000··· 03C9
·· 1:···· 0400··· 05E7
·· 2:···· 1FFE··· 1FFF
·· 3:···· 2020··· 202B
....
0005E0: 0A13 0019 0AAB 0003 ---- ---- ---- ----
001FF0: ---- ---- ---- ---- ---- ---- ---- 0A02
002020: 0A00 FF05 0005 F424 FF00 FF05 ---- ----
I suspect the "0A02" at 1FFE should be at 0FFE.
I had these in the program:
// #include <SX28AC.H>
#include <SX52BD.H>
#include "atd_emu.h"
// #fuses HS,NOPROTECT,NOWDT
// #fuses NOPROTECT,IRC,NOIFBD,NOSYNC,XT2,NOWDT,OPTIONX,IRCTRIM_MAX,BORTRIM3,4PAGE_8BANK
#fuses· HS,NOPROTECT,NOSYNC,NOWDT,IRCTRIM_MAX
Just reporting a bug....
Thanks,
RW Senser
Hi-
Some additional information on this SX-52 error: This error does not occur with the SX-48 (nor with the SX-28).
I'm not sure if the SX-52 is still considered "supported"; my personal view is that it should be <smile>.
Thanks,
RW Senser
This could be because the compiler recognizes the chip as a 2 Kbytes while, it actually is a 4 Kbyte chip. The SX-28 chips has fuses to tell the compiler what size memory it has, while the SX-52 does not do that. So i dont know why this could be hapenning, but i will check to see how the compiler is configuring the device.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Kaushik
CCS Inc.
Brookfield, WI
www.ccsinfo.com
If you have trouble programming a chip, or the chip does not appear to run correctly,
it may well be due to incorrect fuse settings.
Here is a possible workaround that was also posted (by Chris Savage) on the sx/c beta test forum:
·· If you program the device without the PROTECT set you can read the device into the Device Screen and see the fuse options that are listed to confirm them.· If something isn’t setting right you can change it after the read and program the SX from within that window to correct that problem.· I hope this helps.· Take care.
For all those new beta testers that are not yet signed up to the sx/c beta test forum,
request to sign up to the sx/c beta test forum, as it holds vital information what has
been tested (and should have been fixed now).
regards peter
Peter,
thanks for the info about the CCS update site. Before getting access to this site, you need to register with CS first. While doing this, I was asked to enter the locations of three *.crg files. I could not find any of these on my computer. The only one I found was named sxc.crg, so I have filled in this information, hoping that this works. How did you successfully register your copy of SXC?
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Greetings from Germany,
G
I do not have a CD copy of Sx/C, but as I am a member of the sx/c beta test forum,
all I have are downloaded versions. To be able to download an update you need a registration number
and you only get that after purchasing a copy. All the sx/c beta testers that joined the
sx/c beta test forum got a fake purchase (purchase at no $$$) and so we have such
a number. I remember they sent an attachement (.crg file) to my email address
that allowed me to download.
To speed things up I am willing to post the update here, but I need
approval to do this·from Parallax or CCS. If they say I can post it, no problem.
(Any Parallax staff member·reading this?) If not, you must wait for CCS
to grant you access to·download (and this could take a long time).
Edit: the size is 15MB, so no chance posting it here.
If I get approval I could mail it directly to you (if your mailbox can accept 15MB)
Does the CD you got have no instructions how to obtain updates of the product?
If you startup the sx/c IDE, you can try Help->Check for S/W updates
Maybe it is automatically detected that you have a legal copy.
regards peter
·
Post Edited (Peter Verkaik) : 7/24/2007 11:35:15 PM GMT
The cd has no reg number.
Ray,
As for your problems with the SX Tech board, review my previous posts and read the help file regarding direct device programmng...there is some setup that is required at which point it will work fine. I assure you this software is far from crippled if you would just give it a chance.
Jared
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
A wise man who is not known for sure to have existed once said, "Never test a river with both feet." I feel this is especially true in engineering...throughout history everytime something new was tried with little research or planning, the odds were stacked in favor of failure, and everyone knows the house always wins in the long run....
If this happens, close the CCS IDE, go to the directory with the CCS compiler and IDE and open a text file called PCW.INI. Look for the section labeled [noparse][[/noparse]usertools] near the top. You'll see all your command line for your tools have a {{ at the head and tail of them. Using your text editor, do a search and replace, converting {{ to {. Re-start the CCS IDE and the tools should be working again. I have notified CCS of this bug and expect them to fix it soon. Just be aware that anytime you make a change to the user tools via the IDE, the IDE will disable them, and you'll have to follow this process again. It's not hard to do, just annoying.
I have attached a pair of screenshots to show the problem in the GUI. Note how in the tools dialog, all the strings have an extra quote head and tail. This is {{ from the ini file.
Thanks,
PeterM
thank you for the information. In the meantime, CCS has sent me an eMail with the necessary download information for the update. So CCS was much faster this time than you had proposed.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Greetings from Germany,
G
Peter Montgomery will fill us in on the usage at some point, on this thread.
Ken Gracey
I download the SX-Key V3.2.7 and when I try to unzip it, it is asking for a password ???
Bean.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Teacher: What is the difference between ignorance and apathy ?
Student: I don't know and I don't care
Teacher: Correct !
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
www.hittconsulting.com
·
When I try to unzip the SX-Key IDE I downloaded from the link posted in the above message, I am prompted for a password.
Thanks,
Alan Balich
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
"I learn when I succeed, but I learn more when I fail."
Alan Balich
SX/C Wiki - sxcwiki.alanbalich.com
For anyone who is testing the CCS compiler SX/C, there is a BETA version of the SX-Key IDE which should help alleviate some problems. It's BETA, so be aware that there may be some bugs, but it should be stable enough for regular use.
To use it, simply un-zip the contents into an empty directory (not the SX directory with your current SX-Key IDE) and run the program SXKey.exe. It will prompt you to let it install the SX/B compiler, etc. Let it. As long as you install this in a new directory, it won't interfere with you current SX-Key IDE installation.
The following are the bugs that it fixes (not all are SX/C specific):
1 - New COM port enumeration code to find USB serial ports more accurately
2 - Fixed bug that crashed IDE when programming via command line with GUI hidden
3 - Fixed bug that didn't close IDE when COM error occurred during command line execution
4 - Fixed bug where IRC calibration dialog didn't display. It now displays only when "Program" is invoked, not "Debug". It does the calibration during "Debug" programming, but doesn't show the dialog.
In addition, here is the list of command line switches supported by the SX-Key IDE. These are used to set up the "User Tools" in the CCS IDE so it can invoke the SX-Key IDE for things like programming. I have posted this info before, but here it is again:
/r = Load a file as read only
/h = Hide the GUI
/v = Verify after programming
/p = Program the chip for standalone operation
/d = Debug the chip
/da = Debug chip again (do not download code and assume it is the same as the editor window)
/b = Program using files from ByteCraft compiler. (Backward compatibility only. Not needed with the CCS compiler.)
The name of the source file that should loaded MUST be the LAST element on the command line.
For anyone who finds it weird that the CCS IDE doesn't keep using the same IDE over and over, it's because it really should be invoked with the -h switch to hide the editor. By doing this, it makes the SX-Key IDE feel more like a part of the CCS IDE, and it also will do things like automatically close itself after programming is finished.
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.
Please note that all commands and switches in the user tool section of the CCS IDE must have quotes before and after each one separately. Take a look at the existing user tools to see how that works. Also, please see my earlier post in this thread about the bug in the CCS IDE that forces you to edit the PFW.INI file after making changes to the user tools.
Thanks,
PeterM
Post Edited (PJMonty) : 7/27/2007 12:56:41 AM GMT
Parallax
I believe the password is case sensitive, so make sure to capitalize that first P.
For those wondering, "Why is it password protected?" It turns out that the Parallax email server doesn't like it when I send regular ZIP files to Ken. However, it is fine with password protected (e.g. encrypted) ZIP files. In the rush to get it up on the server, I imagine that Parallax simply forgot to re-save the file as a non-password protected ZIP file.
Thanks,
PeterM
It's because the virus scanner scan for filenames within the ZIP. If there is an .EXE or .DLL it gets blocked.
If it's password protected, it cannot scan it.
Bean.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Teacher: What is the difference between ignorance and apathy ?
Student: I don't know and I don't care
Teacher: Correct !
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
www.hittconsulting.com
·
Thank you! I must concur with Bean because Gmail blocks files containing .EXE, thus, I must resort to other tactics when I need someone to send me this types of file.
-Alan
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
"I learn when I succeed, but I learn more when I fail."
Alan Balich
SX/C Wiki - sxcwiki.alanbalich.com
Ray
http://www.ccsinfo.com/scenixupdates.php
regards peter
http://www.ccsinfo.com/scenixupdates.php
This thread is very quiet, is anybody doing any testing?
regards peter
Why throw our cycles at it when they won't respond for months and years at a time? Or haven't in the past.
What bugs were fixed? What work was done? What features were added? Do the example programs actually compile and function? Does it work with the SXKey IDE?
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
---
James Newton, Host of SXList.com
james at sxlist,com 1-619-652-0593 fax:1-208-279-8767
SX FAQ / Code / Tutorials / Documentation:
http://www.sxlist.com Pick faster!
I think the silence says it all about this product.
Ray
http://www.ccsinfo.com/scenixupdates.php
Could CCS inform us about updates via this thread?
Preferably with a What's new file that lists fixes.
regards peter
http://www.ccsinfo.com/scenixupdates.php
A list of changes is here:
http://www.ccsinfo.com/devices.php?page=versioninfo
regards peter
http://www.ccsinfo.com/scenixupdates.php
A list of changes is here:
http://www.ccsinfo.com/devices.php?page=versioninfo
regards peter