catweasle

Never used the command line version. I tried starting the GUI version from a cmd window. First I programmed a spare 18F2550 which went well. Then I simply loaded the 512k hex file for the disPIC33 and the app shut down. No message in the DOS window. Maybe a buffer/memory issue while handling these large hex files but I can not replicate that on the other laptop where I finally had the success. Both are very old Dell, the app crashes on an Inspiron and works on my Latitude. I mentioned above that...

Never used the command line version. I tried starting the GUI version from a cmd window. First I programmed a spare 18F2550 which went well. Then I simply loaded the 512k hex file for the disPIC33 and the app shut down. No message in the DOS window. Maybe a buffer/memory issue while handling these large hex files but I can not replicate that on the other laptop where I finally had success. Both are very old Dell, the app crashes on an Inspirion and works on my Latitude.

Never used the command line version. I tried starting the GUI version from a cmd window. First I programmed a spare 18F2550 which went well. Then I simply loaded the 512k hex file for the disPIC33 and the app shut down. No message in the DOS window. Maybe a buffer issue while handling these large hex files but I can not replicate that on the other laptop where I finally had success. Both are very old Dell, the app crashes on an Inspirion and works on my Latitude.

...oops, I missed your other post further above about AVDD and AVSS and added those. The ICSP port pinout has been changed so I can use my PICkit3 40pin Textool adaptor board with it and that works fine. I managed to fire up an even older Windows laptop (the one I was using is already 10 years old and one of it's USB ports didn't detect your programmer but the others did) and now the application doesn't crash mid programming and finally it worked. Device ID 0x1785 and code verified an all 6 dsPIC33EP512MC502...

...oops, I missed your other post further above about AVDD and AVSS and added those. The ICSP port pinout has been changed so I can use my PICkit3 40pin Textool adaptor board with it and that works fine. I managed to fire up an even older Windows laptop (the one I was using is already 10 years old and has at least one faulty USB port) and now the application doesn't crash mid programming and finally it worked. Device ID 0x1785 and code verified an all 6 dsPIC33EP512MC502 although I did have to restart...

...oops, I missed your other post further above about AVDD and AVSS and added those. The ICSP port pinout has been changed so I can use my PICkit3 Textool adaptor board with it and that works fine. I managed to fire up an even older Windows laptop (the one I was using is already 10 years old and has at least one faulty USB port) and now the application doesn't crash mid programming and finally it worked. Device ID 0x1785 and code verified an all 6 dsPIC33EP512MC502 although I did have to restart...

...oops, I missed your other post further above about AVDD and AVSS and added those. The ICSP port pinout has been changed so I can use my PICkit3 Textool daughter board with it and that works fine. I managed to fire up an even older Windows laptop (the one I was using is already 10 years old and has at least one faulty USB port) and now the application doesn't crash mid programming and finally it worked. Device ID 0x1785 and code verified an all 6 dsPIC33EP512MC502 although I did have to restart...

oops, I missed your other post further above about AVDD and AVSS and added those. The ICSP port pinout has been changed so I can use my PICkit3 Textool daughter board with it and that works fine. I managed to fire up an even older Windows laptop (the one I was using is already 10 years old and has at least one faulty USB port) and now the application doesn't crash mid programming and finally it worked. Device ID 0x1785 and code verified an all 6 dsPIC33EP512MC502 although I did have to restart the...