Forums - *** Failed to detect hardware on Debug Transport 'SPITRANS=USB SPIPORT=0'

16 posts / 0 new
Last post
*** Failed to detect hardware on Debug Transport 'SPITRANS=USB SPIPORT=0'
ignasi.pasqual
Join Date: 8 Mar 17
Posts: 7
Posted: Wed, 2017-03-08 09:07

 

Hi,

 

After checking all the comments on the previous CSR forums, I still have this error. Driver is well installed, transport appears on the CSR_uEnergy with a number and board is connected. Any idea?

 

 

 

Programming flash...

Running 'C:/CSR_uEnergy_SDK-2.6.0.10/tools/bin/make SDK=C:/CSR_uEnergy_SDK-2.6.0.10/tools -f CSRMeshLight.release.mak flash'...

C:/CSR_uEnergy_SDK-2.6.0.10/tools/Makefile.common.uenergy:165: *** Failed to detect hardware on Debug Transport 'SPITRANS=USB SPIPORT=0' Project property: Target Hardware 'CSR101x A05'. Stop.

Finished

 

 

 

Best Regards

 

 

ip

  • Up0
  • Down0
Dr. Nissim Zur
Profile picture
Join Date: 6 Jun 16
Location: Skype: nissim.test CSR1010 External design house
Posts: 235
Posted: Wed, 2017-03-08 10:18

Probably the SPI_PIO is not high.(3V)

 

  • Up0
  • Down0
ignasi.pasqual
Join Date: 8 Mar 17
Posts: 7
Posted: Wed, 2017-03-08 11:30

 

Hi Sir,

 

The SPI switch on the programming board (spi<->usb) is on 3.3V. Any other idea? Thank you in advance

  • Up0
  • Down0
ignasi.pasqual
Join Date: 8 Mar 17
Posts: 7
Posted: Wed, 2017-03-08 11:32

 I'm using the official kit for CSR Mesh

 

https://wiki.csr.com/wiki/CSRmesh

  • Up0
  • Down0
Dr. Nissim Zur
Profile picture
Join Date: 6 Jun 16
Location: Skype: nissim.test CSR1010 External design house
Posts: 235
Posted: Thu, 2017-03-09 00:05

call my skype nissim.test

 

  • Up0
  • Down0
ignasi.pasqual
Join Date: 8 Mar 17
Posts: 7
Posted: Thu, 2017-03-09 00:56

 

Hi Dr nassim,

 

I'm trying to reach you on skype, unsuccesfully. Please, tell me on which schedule works better for you.

 

Best Regards

  • Up0
  • Down0
Dr. Nissim Zur
Profile picture
Join Date: 6 Jun 16
Location: Skype: nissim.test CSR1010 External design house
Posts: 235
Posted: Thu, 2017-03-09 01:45

Any time I am Skype online is OK to call 

  • Up0
  • Down0
ignasi.pasqual
Join Date: 8 Mar 17
Posts: 7
Posted: Wed, 2017-04-05 07:17

 

Hi, I'm still having the same problem. Somebody has any idea?

 

 

  • Up0
  • Down0
ataylorm1
Join Date: 12 Apr 17
Posts: 1
Posted: Sat, 2017-04-15 12:27

I'm running into the same issue.  I have NOTHING connected to my CSR1011 dev board except the provided USB SPI adaptor.  I've been working on a keyboard project and everything was working fine one moment, made a code change (removed a break) and tried to redeploy, and got this error:

Running 'D:/uEnergy_SDK-2.0.0/tools/bin/make SDK=D:/uEnergy_SDK-2.0.0/tools -f keyboard.debug.mak build'...

D:/uEnergy_SDK-2.0.0/tools/Makefile.common.rules.Auto:11: *** Failed to detect hardware on Debug Transport 'SPITRANS=USB SPIPORT=0' Project property: Target Hardware 'Auto Detect'. Stop.

Finished.

 

Now the SPI shows up under the debug transport list, and I can connect to it via hyper term (not that but you get the point), and I can see debug strings coming out (I have it printing out what key I pressed).  But still can't debug.

 

I disconnected EVERYTHING from the dev board except the SPI connection, and still the same issue.

 

I have rebooted, I have unplugged the SPI and dev board, taken a break, come back plugged them in, nothing...

 

Please help!

  • Up0
  • Down0
honek
Join Date: 7 Aug 17
Posts: 4
Posted: Tue, 2017-09-05 08:33

Dear ignasi.pasqual,

I have the same issue with boards included in DK-CSR1010-10184-1B. I get same error 

*** Failed to detect hardware on Debug Transport 'SPITRANS=USB SPIPORT=0' Project property: Target Hardware 'CSR101x A05'. Stop.

 

Finished.

 

 Also CsConfig returns: Error detecting chip type (Read failed on USB-SPI) (Error Code: 11)

 

Did you already resolve your problem?

Thank you for your reply.

Marek

  • Up0
  • Down0
Dr. Nissim Zur
Profile picture
Join Date: 6 Jun 16
Location: Skype: nissim.test CSR1010 External design house
Posts: 235
Posted: Tue, 2017-09-05 12:51

my Skype is nissim.test

I do not see un reply Skype calles. 

please call again, my time is Israel (GMT+3)

click here to see: https://goo.gl/uPzuVJ

 

  • Up0
  • Down0
ignasi.pasqual
Join Date: 8 Mar 17
Posts: 7
Posted: Wed, 2017-09-06 01:09

 

 

Hi Marek,

 

No, we didn't solve it. The general recommendation is not to use this component due to this kind of bugs who don't allow to use it.

 

Good luck

 

ip

  • Up0
  • Down0
honek
Join Date: 7 Aug 17
Posts: 4
Posted: Wed, 2017-09-06 02:18

Hi ignasi.pasqual,

Thank you for your reply. Just to be sure. What do you mean by that recommendation to avoid using that component? Do you mean that development kits DK-CSR1010-10184-1B are  buggy? Where did you hear/read that recommendation? Can you point me on the source?

Thank you. 

Marek

  • Up0
  • Down0
honek
Join Date: 7 Aug 17
Posts: 4
Posted: Fri, 2017-09-08 06:01

To conclude my issue. We have found that our SPI cable delivered with development kit is either wrong or it is designed on purpose  such that  it is not connecting PIO_SEL from CSR USB<>SPI converter to board. 

We did simple measurement. We connected two CSR1010 boards by SPI cable and measured the connection between  PINS on those two boards, GND<->GND, CBS<->CBS, CLK<->CLK and so on (otherwise it would be quite challenging  or even imposible to measure that cable without any test bench :D). Every pair of PINS shows correct connection except PIO_SEL<->PIO_SEL pair. 

If we bring PIO_SEL to high level (to VBAT on board)  then flashing program on board is working. 

Marek

  • Up0
  • Down0
Dr. Nissim Zur
Profile picture
Join Date: 6 Jun 16
Location: Skype: nissim.test CSR1010 External design house
Posts: 235
Posted: Sat, 2017-09-09 09:16

in programming, SPI_PIO must be high 3V). 

If it is not, place a switch and pull it to high when you flash new code. 

 

  • Up0
  • Down0
hainguyen.8y
Join Date: 30 May 18
Posts: 1
Posted: Wed, 2018-05-30 05:57

I have same problem. You have to choose Debug -> Transport again

  • Up0
  • Down0
or Register

Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.