Point logged (one more for Target Management refactoring)
But actually, I guess you are requiring that since M2M Studio doesn’t fit (at all) your needs in Target Management. Our goal is that with the future M2M Studio, it doesn’t matter if the COM port is opened or not on startup, since you won’t need another application to connect to the Wireless CPU
No development tool should interfere with resources that it isn’t actualy using.
While you’re just editing/browsing/building code, there should be no need at all to open the COM port.
eg, the purpose of the app in the Wavecom device might be to communicate with some PC application over the COM port - the development tools shouldn’t interfere with that until it actually comes to downloading & testing.
Ok I get your point.
We usually recommend to dedicate one UART for tools access when making the hardware design, but I can understand the disadvantages of such a solution.
Please be sure that your use case is taken into account.
another route to the same result:
[list=]Start M2M Studio – it “grabs” the COM port, even though it’s not using it;[/list]
[list=]Open SeLiMa[/list]
[list=]Close the opened port[/list]
I get the feeling that this behaviour is caused by selima?
because all the old tools also open the com-port the moment they’re started.
Also just as a pointer to another option.
the mux-config tool is also very handy for connecting m2m studio and hyperterminal (or other software) to the same module