Hi,
I have written already about this problem. But here I am trying to give more details as to what
problems I am encountering.

I have a custom board with BF534 processor. I am using VDSP++5.0 update2 software with 90 day
test drive license. We are getting a few errors when we are trying to connect our target board.
I have given the list of errors which I am encountering. I have also given the error that I am
getting when I run ICE test in continuous scan mode(Error 3).
We are using the following devices in our board.
Flash memory: S29AL0XXD
SDRAM: MT48LCXXM16A2
ALso we are using the flash driver shipped with VDSP++5.0
Our board conforms to the EE-68 note mentioned in ADI site.

Does anyone know how to get around the problem?
PS: We had programmed the board the once already. When we tried to erase the previous program
on the flash and re program it with a new one we are having this problem.

Thank you in advance,
Regards,
Nithin
Error1:

VisualDSP
VisualDSP has detected 0 device(s) in the JTAG
Chain yet there are 1 device(s) listed in this platform

Please verify that all settings are correct in the
ICE configuration utility

Error2:

The target has requested to disconnect from the IDDE

Reason:
GetMem failed

Do you want to disconnect?
    YES    NO
Error3:

Incorrect byte found at position 5686 of test data

Data found:0x52 , expected :0x53

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

Hi Nithin,

If you already tried flashing something in, the problem could be that
whatever has been flashed in is being booted and is corrupting the CPU,
preventing VDSP from connecting.  You need to select a different boot mode
(maybe a SPI or UART slave boot) and then try connecting again.

The flash memory on the BF537 EZKIT is an ST Micro M29W320.  Your flash
device  may be different enough that you need to modify the flash programmer
utility to make it work correctly.

Best regards,

George Kadziolka

Kaztek Systems

www.kaztek.com

From: [mailto:a...@yahoogroups.com] On Behalf Of i...@gmail.com
Sent: Wednesday, May 21, 2008 1:58 AM
To: a...@yahoogroups.com
Subject: [adsp] ADZS_USB_ICE

Hi,
I have written already about this problem. But here I am trying to give more
details as to what problems I am encountering.

I have a custom board with BF534 processor. I am using VDSP++5.0 update2
software with 90 day test drive license. We are getting a few errors when we
are trying to connect our target board. I have given the list of errors
which I am encountering. I have also given the error that I am getting when
I run ICE test in continuous scan mode(Error 3).
We are using the following devices in our board.
Flash memory: S29AL0XXD
SDRAM: MT48LCXXM16A2
ALso we are using the flash driver shipped with VDSP++5.0
Our board conforms to the EE-68 note mentioned in ADI site.

Does anyone know how to get around the problem?
PS: We had programmed the board the once already. When we tried to erase the
previous program on the flash and re program it with a new one we are having
this problem.

Thank you in advance,
Regards,
Nithin

Error1:

VisualDSP
VisualDSP has detected 0 device(s) in the JTAG
Chain yet there are 1 device(s) listed in this platform

Please verify that all settings are correct in the
ICE configuration utility

Error2:

The target has requested to disconnect from the IDDE

Reason:
GetMem failed

Do you want to disconnect?
YES NO

Error3:

Incorrect byte found at position 5686 of test data

Data found:0x52 , expected :0x53

Hi,
I will second George's comment, in the sense that your actual flash could behave differently
(sector sizes, commands, etc) than the one that ADI's driver is supposed to find (M29W320).
So, read bot flashes docs, and figure out yourself if you need to create a custom driver.
However, I guess that chances are that Danville's flasher can handle it for you, so it might be
worth trying to find the info on their website:
http://www.danvillesignal.com/analog-devices-development-tools/sharc-blackfin-programmer.html 
Maybe Al Clark will jump in soon and comment.
Regards,
 
Jaime Andrés Aranguren Cardona
j...@ieee.org
j...@computer.org

----- Original Message ----
From: George Kadziolka <g...@kaztek.com>
To: i...@gmail.com; a...@yahoogroups.com
Sent: Wednesday, May 21, 2008 10:14:46 AM
Subject: RE: [adsp] ADZS_USB_ICE
Hi Nithin,
 
If you already tried flashing something in, the problem could be that whatever has been flashed
in is being booted and is corrupting the CPU, preventing VDSP from connecting.  You need to
select a different boot mode (maybe a SPI or UART slave boot) and then try connecting again.
 
The flash memory on the BF537 EZKIT is an ST Micro M29W320.  Your flash device  may be
different enough that you need to modify the flash programmer utility to make it work
correctly.
 
Best regards,
 
George Kadziolka
Kaztek Systems
www.kaztek.com
 
 
 
From:[mailto:adsp@ yahoogroups. com] On Behalf Of isnithin@gmail. com
Sent: Wednesday, May 21, 2008 1:58 AM
To: adsp@yahoogroups. com
Subject: [adsp] ADZS_USB_ICE
 
Hi,
I have written already about this problem. But here I am trying to give more details as to what
problems I am encountering.

I have a custom board with BF534 processor. I am using VDSP++5.0 update2 software with 90 day
test drive license. We are getting a few errors when we are trying to connect our target board.
I have given the list of errors which I am encountering. I have also given the error that I am
getting when I run ICE test in continuous scan mode(Error 3).
We are using the following devices in our board.
Flash memory: S29AL0XXD
SDRAM: MT48LCXXM16A2
ALso we are using the flash driver shipped with VDSP++5.0
Our board conforms to the EE-68 note mentioned in ADI site.

Does anyone know how to get around the problem?
PS: We had programmed the board the once already. When we tried to erase the previous program
on the flash and re program it with a new one we are having this problem.

Thank you in advance,
Regards,
Nithin

Error1:

VisualDSP
VisualDSP has detected 0 device(s) in the JTAG
Chain yet there are 1 device(s) listed in this platform

Please verify that all settings are correct in the
ICE configuration utility

Error2:

The target has requested to disconnect from the IDDE

Reason:
GetMem failed

Do you want to disconnect?
YES NO

Error3:

Incorrect byte found at position 5686 of test data

Data found:0x52 , expected :0x53 
      

The ADI driver set is limited to the EZ-KIT targets. We try to cover 
most everything popular and we are constantly adding new device support..

We haven't specifically written a driver for the BF534 but we have many 
different BF537 flash combos so I don't think it would be a problem. 
There are literally thousands of combo possibilities so we can't test 
everything. In a few cases, we have had customers supply a sample board 
to fine tune a driver.

We would be glad to work with you.

Al Clark
Danville Signal Processing, Inc.

Jaime Andres Aranguren Cardona wrote:
>
> Hi,
>
>  
>
> I will second George's comment, in the sense that your actual flash 
> could behave differently (sector sizes, commands, etc) than the one 
> that ADI's driver is supposed to find (M29W320).
>
>  
>
> So, read bot flashes docs, and figure out yourself if you need to 
> create a custom driver.
>
>  
>
> However, I guess that chances are that Danville's flasher can handle 
> it for you, so it might be worth trying to find the info on their 
> website: 
>
http://www.danvillesignal.com/analog-devices-development-tools/sharc-blackfin-programmer.html 
>
<http://www.danvillesignal.com/analog-devices-development-tools/sharc-blackfin-programmer.ht
ml>  
>
> Maybe Al Clark will jump in soon and comment.
>
>  
>
> Regards,
>  
>
> Jaime Andrés Aranguren Cardona
> j...@ieee.org
> j...@computer.org 
> <mailto:j...@ieee.orgj...@computer.org> ----- Original Message ----
> From: George Kadziolka <g...@kaztek.com>
> To: i...@gmail.com; a...@yahoogroups.com
> Sent: Wednesday, May 21, 2008 10:14:46 AM
> Subject: RE: [adsp] ADZS_USB_ICE
>
> Hi Nithin,
>
>  
>
> If you already tried flashing something in, the problem could be that 
> whatever has been flashed in is being booted and is corrupting the 
> CPU, preventing VDSP from connecting.  You need to select a different 
> boot mode (maybe a SPI or UART slave boot) and then try connecting again.
>
>  
>
> The flash memory on the BF537 EZKIT is an ST Micro M29W320.  Your 
> flash device  may be different enough that you need to modify the 
> flash programmer utility to make it work correctly.
>
>  
>
> Best regards,
>
>  
>
> George Kadziolka
>
> Kaztek Systems
>
> www.kaztek.com <http://www.kaztek.com/>  
>
>  
>
>  
>
> *From:* [mailto:adsp@ yahoogroups. com] *On Behalf Of *isnithin@gmail. com
> *Sent:* Wednesday, May 21, 2008 1:58 AM
> *To:* adsp@yahoogroups. com
> *Subject:* [adsp] ADZS_USB_ICE
>
>  
>
> Hi,
> I have written already about this problem. But here I am trying to 
> give more details as to what problems I am encountering.
>
> I have a custom board with BF534 processor. I am using VDSP++5.0 
> update2 software with 90 day test drive license. We are getting a few 
> errors when we are trying to connect our target board. I have given 
> the list of errors which I am encountering. I have also given the 
> error that I am getting when I run ICE test in continuous scan 
> mode(Error 3).
> We are using the following devices in our board.
> Flash memory: S29AL0XXD
> SDRAM: MT48LCXXM16A2
> ALso we are using the flash driver shipped with VDSP++5.0
> Our board conforms to the EE-68 note mentioned in ADI site.
>
> Does anyone know how to get around the problem?
> PS: We had programmed the board the once already. When we tried to 
> erase the previous program on the flash and re program it with a new 
> one we are having this problem.
>
> Thank you in advance,
> Regards,
> Nithin
>
> Error1:
>
> VisualDSP
> VisualDSP has detected 0 device(s) in the JTAG
> Chain yet there are 1 device(s) listed in this platform
>
> Please verify that all settings are correct in the
> ICE configuration utility
>
> Error2:
>
> The target has requested to disconnect from the IDDE
>
> Reason:
> GetMem failed
>
> Do you want to disconnect?
> YES NO
>
> Error3:
>
> Incorrect byte found at position 5686 of test data
>
> Data found:0x52 , expected :0x53
>  
------------------------------------