Mloader help needed, PIC18F26K80 not supported?
Posted: Thu Apr 09, 2015 8:36 pm
I'm on a new project trying to make sense of new, to me, tools: EB006V9 programmer, Ghost technology and the mLoader program... the project is a UART-CAN bridge based on PIC18F26K80. Needless to say I run into trouble almost immediately and spent time trying to figure out the issues without much luck.
Specific to this topic... I have the hex file and the chip is inserted into the EB006v9 but do not know if it gets programmed. More so I do not understand if the EB006v9 module works or not.
I load the HEX file then try Autodetect: it says unable to communicate with target. I press Send, says I need to select the chip but the chip I'm using is not available in the <select chip> drop down list. I edited the 8bConfigData.csv (copied the 18F2680 and renamed as 18F26K80). Now I can select the PIC, press Send, it says "the chip could not be detected. Click OK to use specified, D10 flashes a few times and the progress bar shows some activity. Did it program the chip? There is a warning "Flash memory not verified - may be due to code protect). Press Execute does nothing (MCLR high, OSC not running, shouldn't it?). Press Erase, says wait then complete, did it erase? Lastly press Update Bootloader brings up a window displaying version 6:1:9:7. OK this window and an "USB not open" error pops up then "Close programming mode failed" message. I am attaching 2 JPGs to clarify my action sequence.
So what next? Can Matrix add support for this chip in the mLoader? Should I be expecting 19.66MHz on the OSC pins? What should I expect when pressing Execute?
I feel very unproductive at the moment. Please help!
I am using a 9V external power adapter and installed the Matrix supplied driver. The EB006v9 configuration consists of J11 (USB/PSU) set to PSU position (towards the centre of the board), J15 (3V3 or 5V selector) set to 5V (centre of board) and J18/19 selecting the 19.6608 MHz OSC (towards the edge of board).
Plugging the 9V adapter brings in a EB006 Multiprogrammer using Matrix driver 1.0.0.4 as a Custom USB Dev in W7P Device Manager. On the EB006v9 board the D6 LED is on. I measured 5V and 3.3V on the chip. The MCLR line is high. In mLoader the EB006 picture comes up. This indicates that the programmer board works and communicates with the mLoader program, shouldn't it?
Specific to this topic... I have the hex file and the chip is inserted into the EB006v9 but do not know if it gets programmed. More so I do not understand if the EB006v9 module works or not.
I load the HEX file then try Autodetect: it says unable to communicate with target. I press Send, says I need to select the chip but the chip I'm using is not available in the <select chip> drop down list. I edited the 8bConfigData.csv (copied the 18F2680 and renamed as 18F26K80). Now I can select the PIC, press Send, it says "the chip could not be detected. Click OK to use specified, D10 flashes a few times and the progress bar shows some activity. Did it program the chip? There is a warning "Flash memory not verified - may be due to code protect). Press Execute does nothing (MCLR high, OSC not running, shouldn't it?). Press Erase, says wait then complete, did it erase? Lastly press Update Bootloader brings up a window displaying version 6:1:9:7. OK this window and an "USB not open" error pops up then "Close programming mode failed" message. I am attaching 2 JPGs to clarify my action sequence.
So what next? Can Matrix add support for this chip in the mLoader? Should I be expecting 19.66MHz on the OSC pins? What should I expect when pressing Execute?
I feel very unproductive at the moment. Please help!
I am using a 9V external power adapter and installed the Matrix supplied driver. The EB006v9 configuration consists of J11 (USB/PSU) set to PSU position (towards the centre of the board), J15 (3V3 or 5V selector) set to 5V (centre of board) and J18/19 selecting the 19.6608 MHz OSC (towards the edge of board).
Plugging the 9V adapter brings in a EB006 Multiprogrammer using Matrix driver 1.0.0.4 as a Custom USB Dev in W7P Device Manager. On the EB006v9 board the D6 LED is on. I measured 5V and 3.3V on the chip. The MCLR line is high. In mLoader the EB006 picture comes up. This indicates that the programmer board works and communicates with the mLoader program, shouldn't it?