Page 1 of 1

Hardware UART component - PIC32MZ... [Solved]

Posted: Wed Nov 30, 2016 6:09 pm
by Brendan
PIC32MZ continued...

I'm sure they could make a soap opera of this chip, but a recent personal observation when attempting to enable hardware UART.
In simulation all is good, but the problem reveals itself at build time. To confirm, I'm working with PIC32MZ2048EFG144, using the latest Flowcode V7.1.1.0 and have applied the patch of 14/10/2016.

Using software UART with the UART Comms component builds fine, but not with hardware UART.

Selecting channel 1 and mapping Tx and Rx from the drop-down (personally confirmed against the datasheet that all options were valid), and regardless of whether flow control is enabled or disabled, results in the following build error...
C:\Program Files (x86)\Flowcode 7\CAL\PIC32BIT\PIC32BIT_CAL_UART.c: In function 'FC_CAL_UART_Init_1':
C:\Program Files (x86)\Flowcode 7\CAL\PIC32BIT\PIC32BIT_CAL_UART.c:250:12: error: '__IEC0bits_t' has no member named 'U1RXIE'
IEC0bits.U1RXIE = 0;
^
C:\Program Files (x86)\Flowcode 7\CAL\PIC32BIT\PIC32BIT_CAL_UART.c:251:12: error: '__IEC0bits_t' has no member named 'U1TXIE'
IEC0bits.U1TXIE = 0;

Best regards,

Brendan

Re: Hardware UART component - PIC32MZ...

Posted: Fri Dec 02, 2016 10:56 am
by Benj
Hi Brendan,

Right I think I might have this sorted now.

First you need to use our updated UART CAL file which needs to live in the "Flowcode 7/CAL/PIC32BIT" folder.
PIC32BIT_CAL_UART.c
(21.88 KiB) Downloaded 276 times
Next you need to use our updated definition file which needs to live in the "Flowcode 7/FCD/PIC32" folder.
PIC32BIT_CAL_UART.c
(21.88 KiB) Downloaded 276 times
Hopefully these should solve the problem for you, let me know how you get on.

SOLVED: Hardware UART component - PIC32MZ...

Posted: Fri Dec 02, 2016 1:53 pm
by Brendan
Fantastic job !
Thanks Ben.

Following your patches I can confirm that the same project now builds without issue using hardware UART. I'm presently coding in advance of the hardware, though will try to remember to confirm physical operation when possible. Unless proven otherwise - assumed fully resolved :D

Thanks and best regards,

Brendan