MCSPlus serial interface to EasyPIC6 not working?

[Bruce]

Set SW7.1 on for RC7 = RX and SW8.1 on for RC6 - TX

On SW7 & SW8 flip everything else to the OFF position leaving only switches #8 on each one ON. Does it work?

In: http://www.mikroe.com/pdf/easypic6/e...anual_v100.pdf the photo in Figure 6-1 shows both DIP
switches for RC6 & RC7 on switch positions #1.

And just below this in Figure 6-2 they show RC6 & RC7 on DIP switch positions #8. Which is right?

[jellis00]

On SW7 & SW8 flip everything else to the OFF position leaving only switches #8 on each one ON. Does it work?

In: http://www.mikroe.com/pdf/easypic6/e...anual_v100.pdf the photo in Figure 6-1 shows both DIP
switches for RC6 & RC7 on switch positions #1.

And just below this in Figure 6-2 they show RC6 & RC7 on DIP switch positions #8. Which is right?

Tried it both ways, Bruce, while running Mackrackit's code as I modified it above. And as I said in above post to him, no LED test lights turned on, indicating the HSERIN and HSEROUT statements never executed....meaning no receipt of the character I typed on the keboard by the HSERIN.

Any other ideas?

[Bruce]

I always include DEFINE HSER_CLROERR 1 if using HSERIN just to be sure it' never locked up on me, but I'm not sure that's the problem.

Try sending first. Something like HSEROUT ["Hello World",13,10] to MCS terminal. If this doesn't work, then try using SEROUT2 PORTC.6,84,["Hello World",13,10].

If you get nothing on screen, I would check my connection from RC6 to the PC side of the MAX IC, serial cable, etc.

If you have an O-Scope set it in a continuous HSEROUT loop while watching the MAX TX out pin to PC.

[jellis00]

I will try those ideas, Bruce.

Got to wondering if the MCU was actually running. I can see from the PRG light on the EasyPic6 it is getting programmed but in previous code didn't have any way to confirm it was actually running....if it weren't that could explain why the test LEDs didn't light in previous post and also possibly why the HSERIN and HSEROUT statement aren't executing...hence no communications.
I inserted a blinking LED in the loop in the below version and when I run it, it doesn't blink...indicating the MCU is not running!! Now I don't know what to do to make the MCU run.?????

ASM ; 18F2550/4550, 8mhz crystal
   __CONFIG   _CONFIG1L, _PLLDIV_2_1L & _CPUDIV_OSC4_PLL6_1L & _USBDIV_2_1L
   __CONFIG   _CONFIG1H, _FOSC_HSPLL_HS_1H
   __CONFIG   _CONFIG2L, _PWRT_ON_2L & _BOR_OFF_2L & _VREGEN_ON_2L
   __CONFIG   _CONFIG2H, _WDT_ON_2H & _WDTPS_512_2H
   __CONFIG   _CONFIG3H, _PBADEN_OFF_3H ; PortB resets as digital
   __CONFIG   _CONFIG4L, _LVP_OFF_4L & _XINST_OFF_4L

ENDASM
Include "Modedefs.Bas"
INCLUDE "ALLDIGITAL.pbp"    ' Sets all registers for digital ops.
                            ' User must make sure the AllDigital.pbp file 
                            ' is in same directory location as this source
                            ' code before compiling.

DEFINE OSC 16
TRISB = %00001111	' Set PORTB.4,5,6,7 to outputs as test LEDs

ADCON1 = 15		' All I/O pins digital
    PORTB.5 = 0
    PORTB.6 = 0                 ' Turn off the LEDs
    PORTB.7 = 0


X VAR BYTE

    START:
    PORTB.5 = 1         ' Blink LED as test that MCU is running
    RCSTA.4 = 0 : RCSTA.4 = 1
    RCSTA=$90:TXSTA=$20:SPBRG=25
    HSERIN [DEC X]
    PORTB.6 = 1         ' Turn on PortB.6 LED if this statement is executed
                        ' as test of receiving a character
    HSEROUT [DEC X,$d,$a]
    PORTB.7 =1          ' Turn on PortB.7 LED if this statement is executed
                        ' as test of HSEROUT having sent a character
    PORTB.5 = 0
GOTO START

[Bruce]

I've never used this board, but it looks like there's a ton of jumpers on there. And if you're not getting even an LED to blink, I would bet you're just missing a jumper setting!

Might even try replacing the PIC.

Is the POWER LED ON?

[jellis00]

I've never used this board, but it looks like there's a ton of jumpers on there. And if you're not getting even an LED to blink, I would bet you're just missing a jumper setting!

Might even try replacing the PIC.

I just burned a test program into the chip via same programming path I've been using that is a "blinky LED". It works fine. This tells me that at least the MCU chip will run and is OK. However, from what I saw that I described in my previous post, the serial interface code is NOT running in the MCU. Don't know why it would run with one program and not the other???

Is the POWER LED ON?

[/QUOTE] Yes it is.

I just was wondering if it might be the USB to Serial converter cable I have to use because the Laptop I am using doesn't have a true serial (RS232) interface connector. I am using an ATEN UC232A USB-to-serial converter cable that connects to the DB9 connector on the EasyPic6 serial interface. It has a light built in to the serial end of the cable that comes on when the TX and RX switch selections are correct on SW7 and SW9 and the MCU is powered up. I have heard before that some of these USB to serial cables don't always work with some serial interfaces. Have any ideas about this one?
If that isn't it, then it is looking more and more like a failure in one of the compnents in the EasyPic6 serial circuit.....possibly the MAX202 they use...just don't know how to text the circuit to see if it is a H/W failure.
I'm really running out of ideas.

[mackrackit]

You could test the board by removing the PIC and VERY VERY carefully plug a jumper wire in across the PIC TX/RX pin sockets. That will give a loop back to the PC when something is sent.

And/or

Program the chip, put it ina breadboard then connect to the PC. If you have the hardware.
Use SEROUT2 with an inverted MODE then an inverter chip is not needed. Send "hello wold" like Bruce mentioned.

Jump pins 2 and 3 at the USB/serial converter and do a loop back test.

With out an "O" scope, write a code to send something in a loop, something long. with a second pause between sends. Connect a DVM to zero and serial pin #2 of the EasyPic and see it the is any activity from the on-board inverter chip. If the DVM fluctuates then the inverter chip is probably working.