I am following below document for environment setup, porting Uboot on ADSP-SC589 EZ Board:
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.0Licensed under GNU GPL v2Report bugs to <email@example.com>adapter speed: 1000 kHzInfo : ICE-1000 firmware version is 1.0.2Info : clock speed 1000 kHzError: session transport was not selected. Use 'transport select <transport>'Error: Transports available:Error: jtagError: swdin procedure 'init' in procedure 'ocd_bouncer'
What would be the reason for this?
I did following connections,
Let me know if I am missing any connection.
Patched 1.2.0 u-boot images and build&test logs for ADSP-SC589 EZKIT 2.0 board are available from https://ez.analog.com/dsp/software-and-development-tools/linux-for-adsp-sc5xx…
Yes, you are right, the original code in the svn server is just like what you've seen, but we applied 3 patches in buildroot/package/libmcapi, in those patches we enriched our…
The ADSP-SC589 EZKIT 2.0 board has a new Ethernet PHY DP83867, the Linux driver for this new phy is:buildroot/linux/linux-kernel/drivers/net/phy/dp83867.c
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.
I am not able to find the user guide for 1.3.0 release, Can you please share the link of it?
Hi firstname.lastname@example.orgI mean the version of ADI in linux-kernel directory named localversion-adi so that i can make a corresponded patch for you. But anyway i make a patch based on linux-addin-1.2.0 for you. Attach is the patch:
If you have any other questions please let me know.
These patches are not applicable to the kernel version i m using(4.1.39).
Linux kernel 4.1.39 doesn't have sc589-ezkit.dts file and many other files are different in this Kern version.
So can you plz share patches for Linux kernel 4.1.39.
Thanks and Best Regards,
I got your point! Currently ADI released code is based on Linux kernel 4.0.0, you can get the source code from here: https://www.analog.com/en/design-center/evaluation-hardware-and-software/software/LinuxAddin.html#software-relatedsoftware
In our next release Linux-addin 1.4.0, we will upgrade our linux kernel to 4.16.0, here describes the release details: https://ez.analog.com/dsp/software-and-development-tools/linux-for-adsp-sc5xx-processors/f/q-a/104216/upstream-adi-linux/324540#324540
So, for your question, i suggest you changing to an older linux kernel or waiting for the new linux kernel release.
If you have any problems please let me know.
Thanks and best regards,HuanFeng
As you suggested, I downgraded my linux kernel to version 4.0.0, I applied your patches on it.
After that I am run mcapi_blink_test demo program to change the blink rate of LEDs for SHARC1 and SHARC2. I can communicate with SHARC1 and change its LED blinking rate over MCAPI successfully, but same code is not working with SHARC2.
Do you have any idea what might be the reason for this behavior?
Above thread is for same problem(communication issues between arm and sharc2 cores).
Thanks for your information
Please find the below page to update the MCAPI and run the Three-Core Communication Example:
I made some changes in mcapi test code and its working with both SHARC cores.
I am trying to flash uboot image on ADSP SC589 board using ICE-1000 emulator. The indicator LED on Emulator changed from green to purple when i run the batch file, but after some time a dialog box poped up saying "Your firmware version 0.0.2 need to be updated. This may take few minutes."
I clicked "ok" button and purple LED started blinking and after some time I got an error saying "CRC did not match". So I am not able to flash the uboot image.
Can you please let me know what steps i have to follow in order to resolve this.
Note : I flashed same uboot several times using same batch file.
It sounds like you are updating the flash using a Windows machine, is that correct? If so are you also using CCES 2.8.2 for this? Does changing the boot mode to 0 using SW1 on the board change anything? Be sure to change the boot mode and cycle power before trying to update flash. I have never actually seen this error before in this situation so I don't know immediately what is causing it. Hopefully your answers to these questions/comments will help.
I changed boot mode to 0 and it worked.
This issue should be addressed in CCES 2.9.0 which is now released if the issue is what I believe it is.