Even more strange: the example provided with VisualDSP++ for video capture
works flawlessly with SummitICE (haven't tried with HPPCI yet).... the only
difference I see is that in my demo I skip color components, I just store
the luminance, and in theirs they get it, but waste twice the memory.
In my configuration:
//PPI enabled, input mode, active video only, receive field 1&2,
//packing enabled, DMA32 enabled, skipping enabled, skip odd
//elements, 8bit data bus, nothing inverted
*pPPI_CONTROL = SKIP_EN | PORT_EN | FLD_SEL | PACK_EN | DLEN_8 ;
In their configuration:
//PPI enabled, input mode, active video only, receive field 1&2,
//packing enabled, DMA32 enabled, skipping disabled, skip odd
//elements, 8bit data bus, nothing inverted
*pPPI_CONTROL = PORT_EN | FLD_SEL | PACK_EN | DLEN_8 ;
If I run the code from the USB link provided with the kit (EZKit session),
either of the codes work OK; but if I run it from an emulator session
(either HPPCI or SummitICE) only the non-skipping code works.
I've reviewed the HPPCI manual, and the ADSP-BF533-EZLITE schematics, and I
see that all of the VDDIO/BTMS, BTCK, /BTRST and BTDI signals are grounded
on the kit. Does it has some to do with my problem?
Regards
------------------------------
Jaime Andr�s Aranguren Cardona
jaac@sanjaac.com
SanJaaC Electronics
Soluciones en DSP
www.sanjaac.com
"Jaime Andr�s Aranguren Cardona" <jaac@nospam.sanjaac.com> escribi� en el
mensaje news:1113682502.c8e7c8f1bbf5916fc468d15c406827d6@teranews...
> Hello,
>
> I've found the same problem when working on the old SummitPCI emulator.
> Somewhere in my code I configure the PPI like this:
>
> #include <cdefBF533.h>
>
> void Init_PPI(void)
> {
> //The PPI is set to receive 525 lines for each frame
> *pPPI_FRAME = 525;
>
> //PPI enabled, input mode, active video only, receive field 1&2,
> //packing enabled, DMA32 enabled, skipping enabled, skip odd
> //elements, 8bit data bus, nothing inverted
> *pPPI_CONTROL = SKIP_EN | PORT_EN | FLD_SEL | PACK_EN | DLEN_8 ;
>
> }//end Init_PPI
>
> The emulator gets lost exactly after writting to *pPPI_CONTROL.
>
> Any idea of why? Any workaround?
>
> Regards,
>
> --
> ------------------------------
> Jaime Andr�s Aranguren Cardona
> jaac@sanjaac.com
> SanJaaC Electronics
> Soluciones en DSP
> www.sanjaac.com
>
>
> "Jaime Andr�s Aranguren Cardona" <jaac@nospam.sanjaac.com> escribi� en el
> mensaje news:1113681039.8e571c6cb2010cec5ee632c076057bab@teranews...
>> Hi,
>>
>> I'm trying to run a small demonstration aplpication on which I
>> capture images from a camera trough the video codec on the ADDS-
>> BF533-EZLITE (rev 1.1, silicon rev 0.1).
>>
>> This behavior happens both with VisualDSP++ 4.0 and 3.5 Nov'04
>> update, and if using HPPCI emulator:
>>
>> The program loads fine. I can start to run it. But the PPI interrupt
>> never comes back. If I try to halt the DSP, I get the following
>> messages:
>>
>> JTAG scan failed - Check target power and emulator connection.
>> Failed getting full context from the target.
>> Error writing user opcode for breakpoint remove at address:
>> 0xffa0327c.
>> JTAG scan failed - Check target power and emulator connection.
>> Failed getting full context from the target.
>> Error Getting PC after Halting.
>> JTAG scan failed - Check target power and emulator connection.
>> Failed getting full context from the target.
>> JTAG scan failed - Check target power and emulator connection.
>> Failed getting full context from the target.
>>
>> The most strange thing is that it works absolutely flawlessly with
>> the slow EzKit USB link!!! I wanted to use the emulator to get the
>> processed images faster, but does not nork.
>>
>> I am using the HPPCI in legacy mode. Will I need to change to High
>> Speed mode?
>>
>> Has anyone experienced similar problems? Any workaround that you
>> know of?
>>
>> Kindest regards,
>>
>> --
>> ------------------------------
>> Jaime Andr�s Aranguren Cardona
>> jaac@sanjaac.com
>> SanJaaC Electronics
>> Soluciones en DSP
>> www.sanjaac.com
>>
>>
>
>
Reply by ●April 16, 20052005-04-16
Hello,
I've found the same problem when working on the old SummitPCI emulator.
Somewhere in my code I configure the PPI like this:
#include <cdefBF533.h>
void Init_PPI(void)
{
//The PPI is set to receive 525 lines for each frame
*pPPI_FRAME = 525;
//PPI enabled, input mode, active video only, receive field 1&2,
//packing enabled, DMA32 enabled, skipping enabled, skip odd
//elements, 8bit data bus, nothing inverted
*pPPI_CONTROL = SKIP_EN | PORT_EN | FLD_SEL | PACK_EN | DLEN_8 ;
}//end Init_PPI
The emulator gets lost exactly after writting to *pPPI_CONTROL.
Any idea of why? Any workaround?
Regards,
--
------------------------------
Jaime Andr�s Aranguren Cardona
jaac@sanjaac.com
SanJaaC Electronics
Soluciones en DSP
www.sanjaac.com
"Jaime Andr�s Aranguren Cardona" <jaac@nospam.sanjaac.com> escribi� en el
mensaje news:1113681039.8e571c6cb2010cec5ee632c076057bab@teranews...
> Hi,
>
> I'm trying to run a small demonstration aplpication on which I
> capture images from a camera trough the video codec on the ADDS-
> BF533-EZLITE (rev 1.1, silicon rev 0.1).
>
> This behavior happens both with VisualDSP++ 4.0 and 3.5 Nov'04
> update, and if using HPPCI emulator:
>
> The program loads fine. I can start to run it. But the PPI interrupt
> never comes back. If I try to halt the DSP, I get the following
> messages:
>
> JTAG scan failed - Check target power and emulator connection.
> Failed getting full context from the target.
> Error writing user opcode for breakpoint remove at address:
> 0xffa0327c.
> JTAG scan failed - Check target power and emulator connection.
> Failed getting full context from the target.
> Error Getting PC after Halting.
> JTAG scan failed - Check target power and emulator connection.
> Failed getting full context from the target.
> JTAG scan failed - Check target power and emulator connection.
> Failed getting full context from the target.
>
> The most strange thing is that it works absolutely flawlessly with
> the slow EzKit USB link!!! I wanted to use the emulator to get the
> processed images faster, but does not nork.
>
> I am using the HPPCI in legacy mode. Will I need to change to High
> Speed mode?
>
> Has anyone experienced similar problems? Any workaround that you
> know of?
>
> Kindest regards,
>
> --
> ------------------------------
> Jaime Andr�s Aranguren Cardona
> jaac@sanjaac.com
> SanJaaC Electronics
> Soluciones en DSP
> www.sanjaac.com
>
>
Reply by ●April 16, 20052005-04-16
Hi,
I'm trying to run a small demonstration aplpication on which I
capture images from a camera trough the video codec on the ADDS-
BF533-EZLITE (rev 1.1, silicon rev 0.1).
This behavior happens both with VisualDSP++ 4.0 and 3.5 Nov'04
update, and if using HPPCI emulator:
The program loads fine. I can start to run it. But the PPI interrupt
never comes back. If I try to halt the DSP, I get the following
messages:
JTAG scan failed - Check target power and emulator connection.
Failed getting full context from the target.
Error writing user opcode for breakpoint remove at address:
0xffa0327c.
JTAG scan failed - Check target power and emulator connection.
Failed getting full context from the target.
Error Getting PC after Halting.
JTAG scan failed - Check target power and emulator connection.
Failed getting full context from the target.
JTAG scan failed - Check target power and emulator connection.
Failed getting full context from the target.
The most strange thing is that it works absolutely flawlessly with
the slow EzKit USB link!!! I wanted to use the emulator to get the
processed images faster, but does not nork.
I am using the HPPCI in legacy mode. Will I need to change to High
Speed mode?
Has anyone experienced similar problems? Any workaround that you
know of?
Kindest regards,
--
------------------------------
Jaime Andr�s Aranguren Cardona
jaac@sanjaac.com
SanJaaC Electronics
Soluciones en DSP
www.sanjaac.com