Did you know that you can run two
separate instances of the Dios Editor? Why would you want to?
With the creation of the CPslave library. It is very handy to be able to
program the Master and Slave (CoProc) microcontrollers at the same time.
Requirements
The problem comes in when you try to communicate. As you can not have two
chips connected to the same com port.
There are two ways to over come this.
1.
Start the Dios Editor. Then start another copy of the Dios Editor. On the
second copy change the comport but don’t save the settings. This will
allow you to communicate with two different chips.
2.
Copy the Dios Editor short cut. Modify the properties of the second
shortcut. In the target field add the parameter loadcom x
X is the number of the com port to force at load time.
I use com port 1 normally but always keep a shortcut on my
screen to force com port 2 when I need it. Also keep in mind that
there still is only one saved button manager file. Which ever
program you shutdown last will be the button shortcut file loaded. I
also added the "autoupdateno"
command line option to my 2nd desktop icon. This way the auto update
is automatically turned off on the second session.
Here is an example
of the shortcut I use for my second session
Final Notes
Once the two sessions
are open its best to keep the windows separated since it can get quite
confusing as to what belongs to what.
Don't try to actually
program each chip at exactly the same time. Program a 1 chip
then the other. In most cases you will set up a master program with
debug code to help you test your CoProc Code. You CoProc code
can its own debug as well.
