openocd for ADSP-SC589 gives Error: session transport was not selected. Use 'transport select <transport>'

I am following below document for environment setup, porting Uboot on ADSP-SC589 EZ Board:'s_Guide-1.2.0.pdf

When i run openocd command, I am getting following error:

root@nikesh:/opt/analog/cces/2.8.2/ARM/openocd/share/openocd/scripts# /opt/analog/cces/2.8.2/ARM/openocd/bin/openocd -f interface/ice1000.cfg target/adspsc58x.cfg

Open On-Chip Debugger (Analog Devices CCES 2.8.0 OpenOCD 0.9.0-g5030ad7) 0.9.0
Licensed under GNU GPL v2
Report bugs to <>
adapter speed: 1000 kHz
Info : ICE-1000 firmware version is 1.0.2
Info : clock speed 1000 kHz
Error: session transport was not selected. Use 'transport select <transport>'
Error: Transports available:
Error: jtag
Error: swd
in procedure 'init'
in procedure 'ocd_bouncer'

What would be the reason for this?

I did following connections,

  1. Connected power cable to P22.
  2. J2 port of ICE-1000 mounted on P3 port of ADSP-SC589 EZ Board’s P3 port.
  3. MicroUSB-to-USB cable connected to USB to UART port (P8) of EZ Board.
  4. MicroUSB-to-USB cable connected to P1 port of ICE-1000.
  5. Ethernet cable connected to J2 of EZ Board.

Let me know if I am missing any connection.



Top Replies

  • 0
    •  Analog Employees 
    on Jan 17, 2019 10:56 AM over 1 year ago

    Hi Nikesh,

    It looks like you are missing a -f operand before the second script on your command line. The command line should be:

    /opt/analog/cces/2.8.2/ARM/openocd/bin/openocd -f interface/ice1000.cfg -f target/adspsc58x.cfg

    Also, note that if you are using the 1.3.0 kit, there is an updated version of the user guide for the 1.3.0 release within the Docs directory of the kit.


  • Thanks Dave,

    I am not able to find the user guide for 1.3.0 release, Can you please share the link of it?



  • 0
    •  Analog Employees 
    on Jan 18, 2019 11:51 AM over 1 year ago in reply to


    the document (linux_add_in_user_guide.pdf) should be located in the /opt/analog/cces-linux-add-in/1.3.0/Docs directory of you host system once you install the 1.3.0 release of the Linux add-in.

    An online version can also be located here:

  • Thanks Dave,

    I loaded uboot in SPI flash, checkout below log,

    sc # run update
    Speed: 1000, full duplex
    Using dwmac.3100c000 device
    TFTP from server; our IP address is
    Filename 'u-boot.ldr'.
    Load address: 0xc2000000
    Loading: ####################
    3.5 MiB/s
    Bytes transferred = 282752 (45080 hex)
    SF: Detected W25Q128BV with page size 256 Bytes, erase size 4 KiB, total 16 MiB
    SF: 524288 bytes @ 0x0 Erased: OK
    SF: 282752 bytes @ 0x0 Written: OK
    sc # save
    Saving Environment to SPI Flash...
    SF: Detected W25Q128BV with page size 256 Bytes, erase size 4 KiB, total 16 MiB
    Erasing SPI flash...Writing to SPI flash...done
    sc #

    Now, next I am trying to copy Linux kernel image using tftp,

    but i am getting below error:

     Net: Phy 1 not found

    Because of this error i am not able to load Linux Kernel. As per linux_add_in_user_guide_1.3.0.pdf, this can be solved by applying patches on uboot and kernel(as my board Rev is 2.0). I could build uboot but while building kernel below errors:

    Makefile:1358: recipe for target 'doc/' failed
    make[3]: *** [doc/] Error 127
    make[3]: *** Waiting for unfinished jobs....
    make[3]: Leaving directory '/home/nikesh/temp/buildroot/output/build/host-libtool-2.4.5'
    Makefile:1605: recipe for target 'install-recursive' failed
    make[2]: *** [install-recursive] Error 1
    make[2]: Leaving directory '/home/nikesh/temp/buildroot/output/build/host-libtool-2.4.5'
    Makefile:1907: recipe for target 'install' failed
    make[1]: *** [install] Error 2
    make[1]: Leaving directory '/home/nikesh/temp/buildroot/output/build/host-libtool-2.4.5'
    package/ recipe for target '/home/nikesh/temp/buildroot/output/build/host-libtool-2.4.5/.stamp_host_installed' failed
    make: *** [/home/nikesh/temp/buildroot/output/build/host-libtool-2.4.5/.stamp_host_installed] Error 2

    I am stuck at this point, can you please help me here.



  • 0
    •  Analog Employees 
    on Jan 21, 2019 11:46 AM over 1 year ago in reply to

    Hi Nikesh, this sounds like it might be related to the version of the host OS on your build machine, or the packages that you have installed.

    Could you confirm the host OS by performing a lsb_release -a

    For the release testing of the product we develop, build and test using the 32-bit 14.04 LTS release of Ubuntu. There is a section in the User Guide (Environment set up) which details all the packages that are required to build the sources using that host OS.

    If you are using a different host OS (which is likely) then this list of packages may vary.

    I would suggest making sure that all the packages in the user guide are installed before retying the build - it sounds like libtool may be missing. If it still fails we will try and reproduce the error here.