Changes between Version 8 and Version 9 of Boards/Zynq - Zedboard

Timestamp:

02/09/17 02:10:49 (7 years ago)

Author:

Chris Johns

Comment:

Add an example session.

Boards/Zynq - Zedboard

@@ -186 +186 @@
 1. The RTEMS executable is stripped of any debugging information and converted to a binary image and then compressed. Stripping the executable or debugging information does not effect your ability to debug the application because debugging uses the ELF image which still contains the debugging information.
 1. The host tool `mkimage` is built as part of U-Boot. You can find it under `toos/mkimage`. You need to copy it somewhere in your path or add a path so it can be executed.
+
+= RTEMS Libbsd Debugger Application =
+
+The RTEMS Libbsd package builds an RTEMS Debugger application. This test application lets you connect to the running RTEMS application using GDB.
+
+You can find the application in the `rtems-libbsd` build tree:
+
+{{{
+$ ls -las build/arm-rtems4.12-xilinx_zynq_zedboard/debugger01.exe                                                                                                                                                                                                                                                                                                                   
+19745 -rwxr-xr-x  1 chris  user  20171796 Dec 23 14:39 build/arm-rtems4.12-xilinx_zynq_zedboard/debugger01.exe
+}}}
+
+Convert this executable to the U-Boot image format using the script above and copy to the TFTP server then boot the board:
+
+{{{
+U-Boot SPL 2016.05-00598-gb2f1858-dirty (Jun 04 2016 - 15:32:53)
+mmc boot
+Trying to boot from MMC1
+reading system.dtb
+reading uImage
+spl_load_image_fat: error reading image uImage, err - -1
+reading u-boot.img
+reading u-boot.img
+
+
+U-Boot 2016.05-00598-gb2f1858-dirty (Aug 05 2016 - 08:30:10 +1000)
+
+Model: Zynq MicroZED Board
+Board: Xilinx Zynq
+DRAM:  ECC disabled 1 GiB
+MMC:   sdhci@e0100000: 0
+SF: Detected S25FL128S_64K with page size 256 Bytes, erase size 64 KiB, total 16 MiB
+*** Warning - bad CRC, using default environment
+
+In:    serial@e0001000
+Out:   serial@e0001000
+Err:   serial@e0001000
+Model: Zynq MicroZED Board
+Board: Xilinx Zynq
+Net:   ZYNQ GEM: e000b000, phyaddr 0, interface rgmii-id
+
+Warning: ethernet@e000b000 (eth0) using random MAC address - fa:69:35:9e:04:2f
+eth0: ethernet@e000b000
+reading uEnv.txt
+162 bytes read in 10 ms (15.6 KiB/s)
+Importing environment from mmc ...
+Checking if uenvcmd is set ...
+Running uenvcmd ...
+Booting RTEMS XxX from net
+ethernet@e000b000 Waiting for PHY auto negotiation to complete...... done
+BOOTP broadcast 1
+BOOTP broadcast 2
+DHCP client bound to address 10.10.5.247 (257 ms)
+Using ethernet@e000b000 device
+TFTP from server 10.10.5.1; our IP address is 10.10.5.247
+Filename 'zed/rtems.img'.
+Load address: 0x2000000
+Loading: #################################################################
+         ##
+         9 MiB/s
+done
+Bytes transferred = 976253 (ee57d hex)
+## Booting kernel from Legacy Image at 02000000 ...
+   Image Name:   RTEMS
+   Image Type:   ARM RTEMS Kernel Image (gzip compressed)
+   Data Size:    976189 Bytes = 953.3 KiB
+   Load Address: 00104000
+   Entry Point:  00104000
+   Verifying Checksum ... OK
+   Uncompressing Kernel Image ... OK
+## Transferring control to RTEMS (at address 00104000) ...
+*** LIBBSD DEBUGGER 1 TEST ***
+
+RTEMS Shell on /dev/console. Use 'help' to list commands.
+[/] # nexus0: <RTEMS Nexus device>
+cgem0: <Cadence CGEM Gigabit Ethernet Interface> on nexus0
+miibus0: <MII bus> on cgem0
+e1000phy0: <Marvell 88E1512 Gigabit PHY> PHY 0 on miibus0
+e1000phy0:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT-FDX, 1000baseT-FDX-master, auto
+cgem0: Ethernet address: fa:69:35:9e:04:2f
+zy7_slcr0: <Zynq-7000 slcr block> on nexus0
+notice: cgem0: link state changed to DOWN
+add host 10.10.5.1: gateway cgem0
+add net default: gateway 10.10.5.1
+rtems-db: remote running
+rtems-db: tcp remote: listing on port: 1122
+notice: cgem0: link state changed to UP
+}}}
+
+The U-Boot DHCP address may not be the RTEMS IP address. In my case I have a static IP configured in LibBSD:
+
+{{{
+[/] # cat /etc/rc.conf
+cat /etc/rc.conf
+cat: /etc/rc.conf: No such file or directory
+[/] # ifconfig
+ifconfig
+cgem0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
+        options=80008<VLAN_MTU,LINKSTATE>
+        ether fa:69:35:9e:04:2f
+        inet 10.10.5.15 netmask 0xffffff00 broadcast 10.10.5.255
+        inet6 fe80::f869:35ff:fe9e:42f%cgem0 prefixlen 64 scopeid 0x1 
+        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
+        media: Ethernet autoselect (1000baseT <full-duplex>)
+        status: active
+lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
+        options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
+        inet 127.0.0.1 netmask 0xffffff00 
+        inet6 ::1 prefixlen 128 
+        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 
+        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
+}}}
+
+The `ifconfig` command shows the IP address is `10.10.5.15`. We can use this to connect GDB. On the development host run GDB using:
+
+{{{
+$ arm-rtems4.12-gdb -nx build/arm-rtems4.12-xilinx_zynq_zedboard/debugger01.exe
+GNU gdb (GDB) 7.12
+Copyright (C) 2016 Free Software Foundation, Inc.
+License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
+This is free software: you are free to change and redistribute it.
+There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
+and "show warranty" for details.
+This GDB was configured as "--host=x86_64-freebsd10.3 --target=arm-rtems4.12".
+Type "show configuration" for configuration details.
+For bug reporting instructions, please see:
+<http://www.gnu.org/software/gdb/bugs/>.
+Find the GDB manual and other documentation resources online at:
+<http://www.gnu.org/software/gdb/documentation/>.
+For help, type "help".
+Type "apropos word" to search for commands related to "word"...
+Reading symbols from build/arm-rtems4.12-xilinx_zynq_zedboard/debugger01.exe...done.
+(gdb) target remote 10.10.5.15:1122
+Remote debugging using 10.10.5.15:1122
+_Thread_Priority_update (queue_context=0x2866c0) at /opt/work/chris/rtems/kernel/rtems.git/c/src/../../cpukit/score/src/threadchangepriority.c:344
+344       n = queue_context->Priority.update_count;
+(gdb)  info thread 
+  Id   Target Id         Frame 
+* 1    Thread 1.167837697 (UI1  (0a010001), priority(c:254 r:254), stack(s: 32768 a:0x429448), state(DELAY SUSP Wisig)) _Thread_Priority_update (queue_context=0x2866c0) at /opt/work/chris/rtems/kernel/rtems.git/c/src/../../cpukit/score/src/threadchangepriority.c:344
+  2    Thread 1.167837698 (SHLL (0a010002), priority(c:  1 r:  1), stack(s: 32768 a:0x431c08), state(SUSP)) _Thread_Priority_update (queue_context=0x2866c0) at /opt/work/chris/rtems/kernel/rtems.git/c/src/../../cpukit/score/src/threadchangepriority.c:344
+(gdb) kill
+Kill the program being debugged? (y or n) y
+(gdb) q
+}}}
+
+'''Note:'''
+1. The `-nx` is being used to stop loading any `.gdbinit` files. This done when testing the GDB connection. For a real development environment you should create a suitable `.gdbinit` file.
+2. The remote port on the RTEMS target is `1122`. You can configure this in the RTEMS application.
+3. Killing the session using the `kill` command reboots the target. If you have updated the executable on the TFTP before running this command a new version of the application will be download.