[hpsdr] initozy PIPED

Tue Jan 6 11:24:57 PST 2009

----- Original Message ----- 
From: "Bill Tracey" <bill at ewjt.com>
To: "Hulen Smith" <clay1952 at cmaaccess.com>; <hpsdr at lists.hpsdr.org>
Sent: Monday, January 05, 2009 11:24 PM
Subject: Re: [hpsdr] initozy PIPED

> Hulen:
>
> Below you say:
>
>          after PowerSDR load = after initozy = no change
>
> Does this include pressing the Start button on the PowerSDR console
> and thereby turning it on?    I'd expect the fast blink to go away
> when you press the Start button on PowerSDR?

No Bill, fast blink continues at all times after initozy is loaded and relay
clicks. I've made some corrections to "before initozy", sorry but this is
double checked confirmed now with magnifier. All of this is the same no
matter what connector position the boards are in. Maybe it's something in my
Altas board? Tonight I will load it on another computer and see if the
results are the same.

Thanks for your help Bill

>
> Also - what's the date near my call sign (KD5TFD) in the title bar of
> the copy of PowerSDR you have?
>
> Regards,
>
> Bill (kd5tfd)
>
> At 10:45 PM 1/5/2009, Hulen Smith wrote:
> >Bill,
> >
> >I guess I'm not familiar with the sound you're referring to with respect
to
> >the USB cable when plugged into Mercury. I know that the computer
recognizes
> >the Mercury port but wheather or not it is actually communicating with
the
> >port, I don't have any idea. Seems like it's getting something back
because
> >of the success of the FPGA. I'm sure I didn't fully unstand your
question.
> >In any case I'm including the LED's status as compared to your normal
status
> >before and after initozy.
> >
> >----- Original Message -----
> >From: "Bill Tracey" <bill at ewjt.com>
> >To: "Hulen Smith" <clay1952 at cmaaccess.com>; <hpsdr at lists.hpsdr.org>
> >Sent: Monday, January 05, 2009 7:30 PM
> >Subject: Re: [hpsdr] initozy PIPED
> >
> >
> > > Hulen,
> > >
> > > As Phil already mentioned, the I2C writes failing to address 26 would
> > > be expected in a system w/o Janus.   Writes to address 27 are to the
> > > TLV320AIC23B codec on  Penelope, so if it's not present we'd expect
> > > those to fail as well.
> > >
> > > One thing that is of interest is you're getting a Result of False, on
> > > taking the CPU out of reset on the load_firmwareV1.1 call, I get true
> > > for that on my machine, yet you seem to be able to load the FPGA so
> > > I'm not quite sure how significant that result of False is.
> > >
> > > If you run initozy11.bat from a command line before running PowerSDR,
> > > do you hear the Windows sound indicating you've inserted a USB
> > > device?  After the load_firmwareV1.1 call the FX2 on Ozy essentially
> > > reattaches to the PC, so you should here the USB device inserted
> > > tone.    Does it sound normal - on my machine I get a different sound
> > > when Windows can't setup the USB device properly - that would be an
> > > indication of a problem.
> > >
> > > After running initozy11.bat and before running PowerSDR I'd expect
> > > the Ozy LEDs to be:
> > >
before running initozy
D1 = off
D2 = off
D3 = off
D4 = off
D5 = off
D6 = off
D7 = off
D8 = off
D9 = off
D10 = off
D11 = off
D12 = on
> >
after initozy and before "Start"
D1 = fast blink (so many hz I count count)
D2 - D4 = off
D5 - D8 = on
D9 - D10 = alternating
D11 = off
D12 = on
> >
> >after PowerSDR load = after initozy = "Start" = no change
> >
> >
D1 - Fast Blink ( as above)
 D2-4 Off
 D5-8 On
D 9 and 10 Alternating
D11 off
D12 on
> > >
> > > After you run PowerSDR and turn it on LEDs are typically
> > > D1 Off
> > > D2 On
> > > D3 Off
> > > D4-8 On
> > > D 9 and 10 Alternating
> > > D11 off
> > > D12 on
> > >
> > > I assume you're still huniting a no Panadapter Data problem ... if
> > > you could run from a Command line:
> > >
> > > PowerSDR 2>&1 >runlog.txt
> > >
> > > And then turn PowerSDR on, leave it for about a minute, turn it off
> > > and exit.  This will create a file runlog.txt that I'd be interested
> > > to see.   Also would like to know what version of Window's you're
running.
> > >
> > > Cheers,
> > >
> > > Bill (kd5tfd)
> > >
> > > At 04:02 PM 1/5/2009, Hulen Smith wrote:
> > > >***** High Performance Software Defined Radio Discussion List *****
> > > >
> > > >Here's my problem, who can help?
> > > >
> > > >C:\Program Files\FlexRadio Systems\PowerSDR\Release>load_firmwareV1.1
> >0xfffe
> > > >0x0007 ozyfw-sdr1k.hex
> > > >finding busses...
> > > >finding devices...
> > > >usb_get_busses...
> > > >bus location: 0
> > > >Checking for VID PID...
> > > >Found VID PID: fffe 7
> > > >Trying to open device...
> > > >Device handle is: 3499968
> > > >Resetting CPU...Reset ON...
> > > >Result: True
> > > >Opening intel hex file: ozyfw-sdr1k.hex
> > > >Processed 740 lines...
> > > >Result: True
> > > >Taking CPU out of reset...
> > > >Result: False
> > > >Closing device...
> > > >done...
> > > >
> > > >FPGA = SUCCESS
> > > >
> > > >further down
> > > >
> > > >
> > > >C:\Program Files\FlexRadio Systems\PowerSDR\Release>write_i2c 0xfffe
0x7
> > > >0x1a 0x1e 0x00 0x00 2
> > > >finding busses...
> > > >finding devices...
> > > >usb_get_busses...
> > > >bus location: 0
> > > >Checking for VID PID...
> > > >Found VID PID: fffe 7
> > > >Trying to open device...
> > > >Device handle is: 3489664
> > > >Failed to write address: 26
> > > >Closing device...
> > > >done...
> > > >
> > > >INITOZY11 results are the same. Looks like CPU isn't resetting. Clues
> > > >anyone?
> > > >Thanks for any help.
> > >
> >
>

 1231269897.0