AWE server cannot connect to target

16 posts / 0 new
Last post
Shane Hsu
Offline
Last seen: 5 hours 14 min ago
Joined: 09/26/2018 - 6:38pm
AWE server cannot connect to target

Hi I have a ADSP-21489 EZ-Board (http://www.analog.com/en/design-center/evaluation-hardware-and-software/...)

with AWE version: Audio Weaver Designer 6.18.02 Pro

I followed the guide reflashing the board with RS232 through CCES

but when I tried to connect the board via RS-232, I got error message either saying "AWEClient failure: failed,communications error" or "AWEClient failure: failed, transmit error 0xffffd8f1"

 

I've tried the suggestions of changing timeout in the previous post (https://dspconcepts.com/forums/audio-weaver-designer/360-audio-viewer-de...), but it didn't work. Attached is the log file. Can you please help me diagnose this?

Thanks

Shane

 

 

ntalbot
Offline
Last seen: 5 hours 1 min ago
Joined: 07/09/2018 - 1:29pm

Hi Shane,

What RS232 hardware are you using to connect to the board, and did you power cycle the board after flashing the image?We have had intermittent issues in the office with certain RS232 hardware, so this may be related.

Additionally,  where did you get the board image and the version of designer? I have been able to connect with no issues with the current website versions of Audio Weaver Pro and the board image.

Thank you!

Nat

Shane Hsu
Offline
Last seen: 5 hours 14 min ago
Joined: 09/26/2018 - 6:38pm

Thanks Nat,

This is the RS-232 connector I'm using:

https://www.amazon.com/gp/product/B0000VYJRY/ref=oh_aui_detailpage_o01_s...

 

Can you tell me more about power cycle the board? 

I got the board support package and designer from the website last week, so it should be the latest one. 

Shane

ntalbot
Offline
Last seen: 5 hours 1 min ago
Joined: 07/09/2018 - 1:29pm

Hi Shane,

Thanks for the information. Typically, after flashing the board with the image, you need to power cycle it by unplugging the power cable and plugging it back in, in order to reset the board with the new image. I just tried re-flashing the board, and had connection issues before power cycling, but I was able to connect with server with no issues once I power cycled. Let me know if that works.

Thanks!

Nat

Shane Hsu
Offline
Last seen: 5 hours 14 min ago
Joined: 09/26/2018 - 6:38pm

Thanks Nat, I did unplug and plug back after re-flashing it, but it didn't work on my case. One thing I noticed (not sure if it's related) is that before unplugging, all LED lights on the upper right corner were on. After unplugged it, only the left most LED light was on. When I try to connect the board using AWE, the second left LED was on too. 

 
ntalbot
Offline
Last seen: 5 hours 1 min ago
Joined: 07/09/2018 - 1:29pm

Hi Shane,

Have you tried making the connection with different hardware? I am able to connect successfully with a Sabrent USB to Serial adapter with an FTDI chipset (similar to this: https://www.sabrent.com/product/SBT-FTDI/usb-2-0-serial-6-ft-adapter-cab...).

The LED lights are normal and indicate connection -- the leftmost LED should always be on when the BSP has been flashed, and the second from left should be flashing to indicate connection.

Best,

Nat

Shane Hsu
Offline
Last seen: 5 hours 14 min ago
Joined: 09/26/2018 - 6:38pm

Thanks Nat, I just got the recommended Sabrent USB to Serial adapter and tried it. I still got the same error message with the second leftmost LED on without flashing. I'm attaching the error message as well as the port setting. Can you please take a look and see if the setting is the same as yours? Also, if the setting is correct, what's the next thing we should look into? 

Shane

ntalbot
Offline
Last seen: 5 hours 1 min ago
Joined: 07/09/2018 - 1:29pm

Hi Shane,

Thanks for the further information. I have the same settings on my machine, including the same port number, and I am still unable to reproduce the issue. What version of Windows are you running? I have been able to successfully connect on both a Windows 7 and a Windows 10 machine with the same settings.

Otherwise, is there perhaps something interfering with a COM port on your machine, or an issue with the physical connection on the board?

ntalbot
Offline
Last seen: 5 hours 1 min ago
Joined: 07/09/2018 - 1:29pm

Hi Shane,

One further question -- what hardware are you using to flash the  board? I have been using an ICE-2000, but there is a jumper change for use with CCES if you are using different hardware.

Shane Hsu
Offline
Last seen: 5 hours 14 min ago
Joined: 09/26/2018 - 6:38pm

Hi Nat, I'm using the standalone debug agent that comes with the EZ kit. Would that be a problem? Below is the script I used to flash the board and the corresponding log message.

ntalbot
Offline
Last seen: 5 hours 1 min ago
Joined: 07/09/2018 - 1:29pm

Hi Shane,

It shouldn't be a problem using that board, there may just need to be a slightly different jumper setup. How are the jumpers on the bottom of your board currently set up?

Shane Hsu
Offline
Last seen: 5 hours 14 min ago
Joined: 09/26/2018 - 6:38pm

Hi Nat, sorry I'm not quite familiar with the board. Can you tell me more on what jumpers are, and how I can check their setup please?

Thanks

Shane

ntalbot
Offline
Last seen: 5 hours 1 min ago
Joined: 07/09/2018 - 1:29pm

Hi Shane,

Attached is an example of a jumper on the board, in this case the JP3 jumper. The small black component on the pins is a jumper for the two cables. Any set of two pins marked with "JP" is a jumper -- there should be five on the board labeled JP1-JP5. I am testing this debug board in the office and will get back to you ASAP if I can reproduce. Thank you!

Shane Hsu
Offline
Last seen: 5 hours 14 min ago
Joined: 09/26/2018 - 6:38pm

Thanks Nat, it seems that my JP4 is different than yours. If it helps, below are all my jumpers.

ntalbot
Offline
Last seen: 5 hours 1 min ago
Joined: 07/09/2018 - 1:29pm

Hi Shane,

Looking more closely at your build configuration, it seems that you are flashing the SPI binary rather than the RS232 -- in the -file option of the flash command you execute, try entering the file path as "C:\Users\thsu\Desktop\AWE_BSP_adsp-21489_v1.2_Ref\ADI_21489_EZKit\Bin\CCES\21489_EZKIT_RS232.ldr" This should hopefully resolve your problem -- please let me know if this works. Thank you!

Shane Hsu
Offline
Last seen: 5 hours 14 min ago
Joined: 09/26/2018 - 6:38pm

Thanks Nat. I actually tried both SPI and RS232 reflash and attached the wrong screenshot.

BUT, it turned out when I removed the cap of JP4, I'm able to connect to the board! Who would've known that's the problem! Thanks again for going through this process with me Nat!

Shane