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?
Can you also share your bootcmd log?
I am not able to ping from board to my host machine.
Board Network Configuration:
ipaddr = 192.168.0.15
netmask = 255.255.255.0
gatewayip = 192.168.0.1
serverip = 192.168.0.2
Host Network Configuration:
ipaddr = 192.168.0.2
When I power on the board, ethernet LED indicators are glowing at board and host ethernet port, and also LED-4 in ON, but as I run picocom, minicom to take serial access, LED-4 goes OFF and also all LED indicators goes OFF on board and Host machine, what can be the reason for this?
Could you help to confirm the EZ-KIT BOM Version that you are using - it's a small sticker with a version number on the bottom of the board. If it is 2.0, it should be related with the new PHY on ADSP-SC589 2.0 board, please follow https://ez.analog.com/dsp/software-and-development-tools/linux-for-adsp-sc5xx-processors/w/documents/9466/support-for-adsp-sc589-ez-kit-bom-revision-2-0-using-linux-add-in-1-2-0 to apply the new PHY patches to uboot and Linux-kernel. Thanks a lot.
I already tried that, applied patches and tried to load this new uboot and kernel(with patches). But still i am getting same issue of "Net: Phy 1 not found".
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-processors/w/documents/9466/support-for-adsp-sc589-ez-kit-bom-revision-2-0-using-linux-add-in-1-2-0, please help to check it.
Please let me know if you have any questions, thanks a lot.
Can you also share Patched 1.2.0 kernel images.
Thanks Gregchen, it worked with your uboot image, I am able to ping between host and board.
I applied kernel patch and created uImage and loaded it on board using command "run ramboot". Kernel loaded successfully but I am not able to get console(shell prompt), kernel loading gets stucked at below log:
dwmmc_adi mmc.0: num-slots property not found, assuming 1 slot is availabledwmmc_adi mmc.0: IDMAC supports 32-bit address mode.dwmmc_adi mmc.0: Using internal DMA controller.dwmmc_adi mmc.0: Version ID is 270adwmmc_adi mmc.0: DW MMC controller at irq 102, 32 bit host data width, 1024 deep fifodwmmc_adi mmc.0: No vmmc regulator founddwmmc_adi mmc.0: No vqmmc regulator founddwmmc_adi mmc.0: 1 slots initializedBlackfin hardware CRC crypto driverbfin-hmac-crc 31001200.crc: initializedbfin-hmac-crc 31001300.crc: initializedusbcore: registered new interface driver usbhidusbhid: USB HID core drivericc 20080000.icc: initializedTCP: cubic registeredNET: Registered protocol family 17can: controller area network core (rev 20120528 abi 9)NET: Registered protocol family 29can: raw protocol (rev 20120528)can: broadcast manager protocol (rev 20120528 t)can: netlink gateway (rev 20130117) max_hops=1do_initcall_level level 7ThumbEE CPU extension supported.console [netcon0] enablednetconsole: network logging startedrtc-adi2 310c8000.rtc: setting system clock to 1970-01-01 00:34:27 UTC (2067)IP-Config: Complete: device=eth0, hwaddr=02:80:ad:20:31:e8, ipaddr=192.168.0.15, mask=255.255.255.0, gw=192.168.0.1 host=sc58x, domain=, nis-domain=(none) bootserver=192.168.0.2, rootserver=192.168.0.2, rootpath=ALSA device list: No soundcards found.Freeing unused kernel memory: 16896K (c0524000 - c15a4000)random: dd urandom read with 37 bits of entropy availablestmmaceth 3100c000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/txrandom: nonblocking pool is initialized
There is not progress after this and not able to get shell console.
Can you please share Patched 1.2.0 kernel images.
I am able to boot the board with our patched uImage. I loaded uboot using tftp, and also able to load kernel but when i restart the board, uboot doesnt get loaded. I have to load it from gdb every time i reboot the board. Can you let me know how can I save uboot to flash memory so that it will get loaded every time i reboot the board.
this is documented in the User Guide (version 1.2.0 of the User Guide lists the steps in section 2.1.3 Flashing U-Boot for the first time).
It is strongly recommended that when starting out that users follow all instructions in Chapter 2 of the User guide to avoid problems while getting the system up and running.
I did these steps many times, its not working as expected. In document, in section "Flash U-Boot to SPI Flash", after loading uboot and saving it, its asked to "BMODE switch set to position 1". So what should be the position of BMODE switch while flashing U-Boot for first time?