Hi Phil,
Well I had family in town this weekend, so I didn't get around to going to 115.2KBPS, however, I'm shooting for next weekend. I saw you added a few lines to the code to turn everything off before vixen runs, any other changes? Do you think you could release a new version of the FW this week? I've been strongly encouraging all XMUS users stick with: Renard-20070812_57600_EXTOSC_NoPWM.asm because it was known to work, and thus far, no probelms have been reported.
But now would be the time to take that next step, for us to roll in all the changes you have made since August, and whatever new features you would like to test on a large scale.
I'll be configuring it for 115.2 EXTOSC NoPWM and posting it externally (asm and hex), so if you have a little time this week, kindly fire off the code and we'll start pounding on it, and get some feedback to you.
Seems like early in the year, nobody has enough channels setup to test stuff, and by the time they do have their displays setup, it is a mad rush for Christmas, so now that we are post-season, and the display is still up, this is the perfect time to do some experimentation for a few weeks.
Thanks for the great FW Phil,
Dave
Attempted 115200 tonight. No luck. The 20070815a diag code is reporting:
'one-shot' rx_okay LED
'one-shot' rx_frame_error LED
I used the following config:
From the Diag code:
;; units in Hz for the following rate constants
#define CLOCKRATE 18432000
#define BAUDRATE 115200
#define TIMERRATE 30720
Running Vixen 2.0.5.0.
Besides the diag code I tested with Renard 20070907 using PWM.
;; PWM_build can be either 0 or 1
#define PWM_build 1
;; DC_build can be either 0 or 1 (it should be 0 if PWM_build is 0)
#define DC_build 0
#define CLOCKRATE 18432000
#define BAUDRATE 115200
;;;;;;;;;;;;;;;;;;57600 Stemple 9-21-2007
;;;;;;;;;;;;;;;;;;115200 Stemple 1-03-2008
;; CTR_LOCKOUT should be 1 for the DC build, can be a somewhat larger number
;; for non-PWM or non-DC builds.
#define CTR_LOCKOUT 15
;; For positive_true outputs, remove the following define (normally, this
;; should be left in place).
#define OUTPUT_NEGATIVE_TRUE
I didn't get any sign of communication. The LEDs lite random as usual.
ms
I don't know if this test was supposed to be for any specific board type but I tried to run 115.2 on my system of 2 Ren24s and 2 595/Ren_C combos spread over three serial ports. No action. No blinky. No flashy. No dimmy.
Hey Phil, do you mind if i post the latest beta FW here for others to experiment with?
Phil sent me some code last week for this experiment, haven't fired it up yet....
I'd rather wait a few hours until I've had a chance to fire it up, just in case there was something stupid in the code.
--
Phil
OK, I finally got around to firing it up. That file that I sent to xmus has a minor typo error (a '1' accidently inserted at the beginning of line 371).
It appeared to work for a moment, then became erratic. When I looked at the serial signal coming into the PIC on a scope it appeared that the baud rate was way off (125000 instead of 112500). That was going through a Belkin serial adaptor, so I'm off to find a serial cable for that PC.
--
Phil
I gave up on the usb to serial cable ...
ms
The serial port on the PC works a lot better.
--
Phil
Phil,
I think you have it resolved, but I over ordered usb->serial adapters (I have several extra) I'm happy to launch you one. Just PM me with your address.
Xmus,
Have you looked at the output with a scope? What I saw today came as a complete surprise to me. Even the 57600 output was a touch high, at 59000 or so, and loading the official Belkin drivers didn't help any.
Anyway, here is the latest firmware. It is set up for 57600, non-PWM usage.
--
Phil
