hserout issues on the 18F26K83

[rocket_troy]

I've set the hardware config totally manually from the datasheet and via PBP defines (suggested in the supplementary document PIC18FxxK42_notes) and many hybrids of the 2 methods.

OSCFRQ = %1000 '64Mhz
Define OSC 64

'******************************************************************************
'Configure UART Control Register 0
U1CON0.7 = 1 'BRGS = 1 (high speed baud generator)
U1CON0.6 = 0 'ABDEN = 0 Auto-baud Detect Disabled 
U1CON0.5 = 1 'TXEN: Transmit Enabled
U1CON0.4 = 0 'RXEN: Receive Disabled
U1CON0.3 = 0 '0000 = Asynchronous 8-bit UART mode
U1CON0.2 = 0 '0000 = Asynchronous 8-bit UART mode
U1CON0.1 = 0 '0000 = Asynchronous 8-bit UART mode
U1CON0.0 = 0 '0000 = Asynchronous 8-bit UART mode

U1CON1.7 = 0 'Turn Serial port 1 off for baud setting
 
U1BRGL = 138  'Baud Divisor low byte
U1BRGH = 1    'Baud Divisor high byte
U1RXPPS = %1011 'Assign UART RX pin to RB3
RB0PPS = %010011  'Assign UART1 TX pin to RB0
U1CON1.7 = 1 'Turn Serial port 1 on

and the more straightforward method:

Define OSC 64
DEFINE HSER_RXREG PORTB
DEFINE HSER_RXBIT 3
DEFINE HSER_TXREG PORTB
DEFINE HSER_TXBIT 0
DEFINE HSER_BAUD 115200

If that was the issue, then why does everything in the quote marks come through okay?

Regards,

Troy

[rsocor01]

Use a logical analyzer to see what's coming out of the chip. Compare the output of the SEROUT2 to the output of the HSEROUT2 using the logical analyzer. You might think that your output is 115200, but it is not. I suspect that you have it set up for another baud rate. Also, check if you have the data configured as 8N1.

[rocket_troy]

Again, if I have it set up as another baud rate, then why is every text string in quotation marks coming through fine?

Troy

[rocket_troy]

Okay, I think I might have solved this one. I didn't have the TRIS of the transmit pin configured as an output. I was under the erroneous impression the UART controller trumped control of any port setting while active. I misinterpreted page 463 of the datasheet:
"When TXEN is set and the transmitter is not idle, the TX pin is automatically configured as an output. When the transmitter is idle, the TX pin drive is relinquished to the port TRIS control"

Damn these serial issues have been throwing some curveballs at me recently. Just transmitting enough correct data to totally throw me off the scent... damn it...

Troy

[rsocor01]

If you connect a logical analyzer to the serial lines, you know for sure if data is being transmitted or not. That would have saved you a lot of time. I always put in my PCB designs a testing point for all the serial data lines.

[HenrikOlsson]

I've been having some issues lately, not with that device specifically but with MCS Serial Communicator (or so it seems). I'm communicating with my board using simple ASCII commands at 57600 baud. Single letter/digits commands (like '?' works most of the time, multi letter/digit commands (like 'P100' works sometimes but most often not.

Thing is, if I use TeraTerm instead everything works perfectly, same computer, same USB cable, same FTDI adapter, same board. Disconnect Serial Communicator and connect TeraTerm to the same virtual COM port and it just works. I have no idea what's going on, before trying TeraTerm I even changed the PIC chip on the board cause I figured I've damaged the UART pins somehow but needless to say the new chip behaved exactly the same.

Anyone else seen anything like this when using Serial Communicator built into MicroCode Studio?

I'm going to put the scope and/or logic analyzer on it and see if I can see anything different.

/Henrik.

[rocket_troy]

I didn't even realize that MCS & MCSX had a Serial Communicator [blush]. Been using them for... dunno... 20+ years and never noticed. The only defence I have is I'm only an occasional user/coder.

Troy

[tumbleweed]

...Single letter/digits commands (like '?' works most of the time, multi letter/digit commands (like 'P100' works sometimes but most often not.

This could be due to your code and how the two terminals work. MCS will send the data when you click 'send', or when you hit 'Enter' if you have the transmit window setting 'Transmit on carriage return' checked.

For TeraTerm, this is configurable (char vs line mode), but typically it's set to transmit as the individual chars are entered.