Sign in

username:

password:



Not a member?

Search rabbit-semi



Search tips

Subscribe to rabbit-semi



Ads

Discussion Groups

See Also

DSPFPGAElectronics

Discussion Groups | Rabbit-Semi | Serial port A


Advertise Here

This is a group for folks designing and programming embedded systems using the Rabbit Semiconductor C-programmable microcontroller. Rabbit Semi is a spin-off from Z-World who makes a variety of embedded modules and tools. This group is not affiliated with either Rabbit or Z-World, but is a user forum for sharing ideas, asking questions, flaunting knowledge, and other typical user group stuff. The Rabbit is a powerful uC, supported by a full-featured C-compiler.

Serial port A - Maurits van de Kamp - Oct 23 14:45:15 2009

Hi all,

I've been away for a while since I quit my job making Rabbit software
a few years ago, but now I have the occasional freelance project and
I'm back to share the fun. :)

Well, and a problem of course ;-)

I'm making a device based on an RCM3700 that needs lots of serial
ports. So many that I need to use port A as well, which is normally
the programming port. So, after the programming is done I attach a
little internal cable that links the Rabbit's programming port to a
serial connector on the box and all should be ok.

However, it seems I can only receive data on that port, but nothing
goes out. The program is of course compiled without rst-28
instructions and all debugging code is removed. Is there something in
software I need to set to be able to use port A as a normal serial
port, besides the obvious serAopen()? I can't find anything in the
docs specifically related to port A. The other ports work fine.

Thanks for any help :)

Maurits.

------------------------------------



(You need to be a member of rabbit-semi -- send a blank email to rabbit-semi-subscribe@yahoogroups.com )


Re: Serial port A - Steve Trigero - Oct 23 15:16:17 2009

I do the very same thing of using Port A
for programming, and the application using
it as a standard com port. And there is
nothing special you need to do.

How did you determine your app is receiving?
If by using an o'scope, it could be the baud
rate is not correct.

Steve

________________________________
From: Maurits van de Kamp
To: r...@yahoogroups.com
Sent: Fri, October 23, 2009 10:00:18 AM
Subject: [rabbit-semi] Serial port A

Hi all,

I've been away for a while since I quit my job making Rabbit software
a few years ago, but now I have the occasional freelance project and
I'm back to share the fun. :)

Well, and a problem of course ;-)

I'm making a device based on an RCM3700 that needs lots of serial
ports. So many that I need to use port A as well, which is normally
the programming port. So, after the programming is done I attach a
little internal cable that links the Rabbit's programming port to a
serial connector on the box and all should be ok.

However, it seems I can only receive data on that port, but nothing
goes out. The program is of course compiled without rst-28
instructions and all debugging code is removed. Is there something in
software I need to set to be able to use port A as a normal serial
port, besides the obvious serAopen()? I can't find anything in the
docs specifically related to port A. The other ports work fine.

Thanks for any help :)

Maurits.



(You need to be a member of rabbit-semi -- send a blank email to rabbit-semi-subscribe@yahoogroups.com )

Re: Serial port A - Rabbit - Oct 23 16:31:24 2009

switch 2 COM ports in your program and check if the new port is working
- this way you can check your software.
George

Maurits van de Kamp wrote:
>
>
> Hi all,
>
> I've been away for a while since I quit my job making Rabbit software
> a few years ago, but now I have the occasional freelance project and
> I'm back to share the fun. :)
>
> Well, and a problem of course ;-)
>
> I'm making a device based on an RCM3700 that needs lots of serial
> ports. So many that I need to use port A as well, which is normally
> the programming port. So, after the programming is done I attach a
> little internal cable that links the Rabbit's programming port to a
> serial connector on the box and all should be ok.
>
> However, it seems I can only receive data on that port, but nothing
> goes out. The program is of course compiled without rst-28
> instructions and all debugging code is removed. Is there something in
> software I need to set to be able to use port A as a normal serial
> port, besides the obvious serAopen()? I can't find anything in the
> docs specifically related to port A. The other ports work fine.
>
> Thanks for any help :)
>
> Maurits.
------------------------------------



(You need to be a member of rabbit-semi -- send a blank email to rabbit-semi-subscribe@yahoogroups.com )

Re: Serial port A - Maurits van de Kamp - Oct 24 2:16:42 2009

> How did you determine your app is receiving?
> If by using an o'scope, it could be the baud
> rate is not correct.

No, I can tell because the serial port is used as a configuration
console that is also reachable through telnet. When I hit enter on
the console port, the telnet port gets disabled (as I programmed it
to) until I blindly type the login name and password and then exit
the menu again on the console. So yes it's receiving me perfectly and
the baudrate is ok. :) There's just nothing coming out.

Back to the hardware I guess.. :)

Thanks!

Maurits.


(You need to be a member of rabbit-semi -- send a blank email to rabbit-semi-subscribe@yahoogroups.com )

Re: Serial port A - Steve Trigero - Oct 24 23:04:54 2009

So there is more going on with the port than
just a simple serial port connection as your
post implied. That would have been nice to know.

________________________________
From: Maurits van de Kamp
To: r...@yahoogroups.com
Sent: Fri, October 23, 2009 11:14:43 PM
Subject: Re: [rabbit-semi] Serial port A

How did you determine your app is receiving?
>If by using an o'scope, it could be the baud
>rate is not correct.
>

No, I can tell because the serial port is used as a configuration console that is also reachable through telnet. When I hit enter on the console port, the telnet port gets disabled (as I programmed it to) until I blindly type the login name and password and then exit the menu again on the console. So yes it's receiving me perfectly and the baudrate is ok. :) There's just nothing coming out.

Back to the hardware I guess.. :)

Thanks!

Maurits.



(You need to be a member of rabbit-semi -- send a blank email to rabbit-semi-subscribe@yahoogroups.com )

RE: Serial port A - "Fournier, Pete" - Oct 26 9:30:38 2009

Make it simpler, just to test!
-Pete

________________________________

From: r...@yahoogroups.com [mailto:r...@yahoogroups.com]
On Behalf Of Maurits van de Kamp
Sent: Saturday, October 24, 2009 2:15 AM
To: r...@yahoogroups.com
Subject: Re: [rabbit-semi] Serial port A

How did you determine your app is receiving?
If by using an o'scope, it could be the baud
rate is not correct.

No, I can tell because the serial port is used as a configuration
console that is also reachable through telnet. When I hit enter on the
console port, the telnet port gets disabled (as I programmed it to)
until I blindly type the login name and password and then exit the menu
again on the console. So yes it's receiving me perfectly and the
baudrate is ok. :) There's just nothing coming out.

Back to the hardware I guess.. :)

Thanks!

Maurits.



(You need to be a member of rabbit-semi -- send a blank email to rabbit-semi-subscribe@yahoogroups.com )

Re: Serial port A - adrianmojoatca - Oct 26 10:51:03 2009

Hi,
If you are using, for you program, separate instructions and data spaces, you should modify the rabbitbios.c at (approx) line 1319 in the following way:

// Make serial A fast. Use relay if you want interrupt to be modifiable.
#rcodorg sera_intvec apply
// jp DevMateSerialISR
// Uncomment the following line and comment out the preceding line if relay is desired.
INTVEC_RELAY_SETUP(intvec_relay + SERA_OFS)

This should let you send/receive properly on the serial port A.

--- In r...@yahoogroups.com, Maurits van de Kamp wrote:
>
> Hi all,
>
> I've been away for a while since I quit my job making Rabbit software
> a few years ago, but now I have the occasional freelance project and
> I'm back to share the fun. :)
>
> Well, and a problem of course ;-)
>
> I'm making a device based on an RCM3700 that needs lots of serial
> ports. So many that I need to use port A as well, which is normally
> the programming port. So, after the programming is done I attach a
> little internal cable that links the Rabbit's programming port to a
> serial connector on the box and all should be ok.
>
> However, it seems I can only receive data on that port, but nothing
> goes out. The program is of course compiled without rst-28
> instructions and all debugging code is removed. Is there something in
> software I need to set to be able to use port A as a normal serial
> port, besides the obvious serAopen()? I can't find anything in the
> docs specifically related to port A. The other ports work fine.
>
> Thanks for any help :)
>
> Maurits.
>

------------------------------------

______________________________
controlSUITE™ software. Comprehensive. Intuitive. Optimized.
Real-world software for real-time control. Details Here!



(You need to be a member of rabbit-semi -- send a blank email to rabbit-semi-subscribe@yahoogroups.com )

Re: Re: Serial port A - Maurits van de Kamp - Oct 26 11:08:26 2009

> If you are using, for you program, separate instructions and data
> spaces, you should modify the rabbitbios.c at (approx) line 1319 in
> the following way:

Aahh.. this is exactly the kind of hidden mysterious bug/feature
stuff I was hoping to be the cause of this. :) I don't have the
hardware at hand right now but I'll give this a try tomorrow!

Maurits.

------------------------------------



(You need to be a member of rabbit-semi -- send a blank email to rabbit-semi-subscribe@yahoogroups.com )