On Mon, 23 Apr 2007 08:06:55 -0400, you wrote: >Thanks Gerhard, that explains when >I ran two instances of MPLAB with ICE2000 and ICD-2 (PIC16F57 & PIC16F913) >talking to each other. Mostly worked but save on exit made for some proble= m. > >Guess I'll have to run two computers and KVM switch between the two. >Oh' well. >Thanks, >Ray > > > > >On Mon, 23 Apr 2007 08:35:50 -0300, Gerhard Fiedler wrote: >>=A0Xiaofan Chen wrote: >> >>>>=A0I don't think so, though. I think this would require two >>>>=A0instances of MPLAB (since MPLAB doesn't seem to have built-in >>>>=A0support for two ICD2 devices), and I don't think you can run >>>>=A0two instances of MPLAB. >>>> >>> >>>=A0You can. >>> >>>=A0The trick: to use different workspace for MPLAB. >>>=A0http://forum.microchip.com/tm.aspx?m=3D195112 >>> >>=A0Ah, makes sense. Just keep in mind that probably any settings that >>=A0are MPLAB application settings (like whether the programmer powers >>=A0the target) will get saved in the state of the instance you close >>=A0last. >> >>=A0I always find it strange that the programmer/debugger settings are >>=A0application settings and not workspace settings. When I have >>=A0different requirements for different projects, I expect that to be >>=A0stored with the project workspace -- but nooo. Not sure how the >>=A0guys at Microchip work with this :) >> >>=A0Gerhard Yes - I ran into this when I was running two MPLAB-ICE2000's, one parallel = & one USB. = It would frequenctly find the wrong one, and then you got the cascade of er= ror messages about being the wrong processor type ( but it still ploughed on regardless, resulting i= n more errors, and sometimes complete crashes.). = The main fix was to only have one ICE2000 switched on when starting the fir= st instance, so it either found it, or failed, and in the latter case you could change the IO setting= without having to wait for all the errors to happen. . The one thing that can be a real killer is if you have the 'automatically r= eopen last workspace' option set, the last WS used ICE2000 and ICE2000 is either no longer connec= ted or has a differnt PCM plugged in. It can get into the situation where it will always crash on sta= rtup and the only way to recover is to manually edit the config file. = -- = http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist