Page 1 of 1

ECIO 40P Issues

Posted: Sat Jul 22, 2023 11:47 am
by steve001
Morning All,

Not used my ECIO's for a long time and having some issues, and confused what the issue(s) could be.

Installed the 64 Bit Drivers for the 28 & 40 P and trying to compile to target the USB HID example on the V9 wiki

https://www.flowcode.co.uk/wikiv9/index ... D_Keyboard

First issue ?

plugging in my ECIO to check windows detected it :-
Capture2.PNG
Capture2.PNG (69.34 KiB) Viewed 3298 times
Have tried a different port and get the same message.
Have tried the same lead on my electronic load and it works ok.

So i thought maybe because flowcode not open, so i opened it

When i checked the project options to try and change to mloader as my default is a pickit3 - was greeted by this message :-
Capture1.PNG
Capture1.PNG (66.23 KiB) Viewed 3298 times
My ECIO is set to USB Power on the Link & the green led flashes

running mloader i get this but forget what to do next, seams like everything knows its there
Capture3.PNG
Capture3.PNG (60.48 KiB) Viewed 3292 times
Any idea's



Steve

Re: ECIO 40P Issues

Posted: Sun Jul 23, 2023 12:45 pm
by steve001
Afternoon All,

Having Problems Still.

Very hit and miss if my ECIO programs or not, pressing "compile to chip"


Title:
Description:
Device: PIC.18F.ECIO-40
Generated by: Flowcode v9.3.1.36
Date: Sunday, July 23, 2023 12:30:49
Users: 1
Registered to:
Licence key:
https://www.flowcode.co.uk
Using FCD settings for compiler
Launching the compiler...
C:\Program Files (x86)\Flowcode\Common\Compilers\picv2\bin\xc8.exe --chip=18F4455 "USB_HID_Keyboard.c" --MSGDISABLE=359,1273,1388 --CODEOFFSET=800h --ROM=default,-0-7FF
C:\Program Files (x86)\Flowcode\Common\Compilers\picv2\pic\bin\picc18 --chip=18F4455 USB_HID_Keyboard.c --MSGDISABLE=359,1273,1388 --CODEOFFSET=800h --ROM=default,-0-7FF
Microchip MPLAB XC8 C Compiler V2.10
Build date: Jul 30 2019
Part Support Version: 2.10
Copyright (C) 2019 Microchip Technology Inc.
Employing 18F4455 errata work-arounds:
* Corrupted fast interrupt shadow registers
* No stopping on H/W breakpoints after NOP2
USB_HID_Keyboard.c: FCM_ASCIIToKeypress()
1147: case '£':
^ (226) char const too long
(908) exit status = 1
(908) exit status = 1

C:\Program Files (x86)\Flowcode\Common\Compilers\picv2\bin\xc8.exe reported error code 0x1

Autoclose turned off


FINISHED
[/code]

Dont understand what is going wrong

at the moment mloader is seeing the ECIO and the LED is flashing (dose this mean its connected to mloader) ?
Device manager is showing it the ECIO logo is green
I am unable to compile to chip or to hex


Any idea's

Steve

Re: ECIO 40P Issues

Posted: Sun Jul 23, 2023 1:48 pm
by medelec35
Hi Steve the '£' ect is a part of the extended ASCII set and that is what's causing the error.
If you disable the Switch icon that contains '£' and any other extended chars, you should find it compiles OK.

Re: ECIO 40P Issues

Posted: Sun Jul 23, 2023 4:31 pm
by steve001
Hi Martin,

Thank you.
Would you be able to modify the example file in the V9 wiki please?

I am not 100% sure and don't feel confident i can modify my chart correctly as i am stepping through and trying to get my head around what happening and why.

https://www.flowcode.co.uk/wikiv9/index ... D_Keyboard

Steve

Re: ECIO 40P Issues

Posted: Sun Jul 23, 2023 5:10 pm
by chipfryer27
Hi Steve

In the ASCIItoKeypress Macro chart you will see two decision switches. The first has options for 0-9, the second with characters such as ")" etc.

If you open up the properties for this switch and change "£" to say "+" or any other non extended character i.e. anything decimal 0-127 then it should compile fine.

ASCII codes are here https://www.asciitable.com/

Regards

Re: ECIO 40P Issues

Posted: Mon Jul 24, 2023 8:55 am
by steve001
Hi Iain,

Thank you i think i get it. I will have a go later

Steve

Re: ECIO 40P Issues

Posted: Tue Jul 25, 2023 6:07 pm
by steve001
Hi All,

The application that i was wanting to use this for has, changed this is no longer required.
This project is of interest to me so i will have a go later

Thanks for the advice so far.
I will pick this up again at some point

Steve