From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31588 invoked by alias); 6 Apr 2013 09:49:50 -0000 Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Received: (qmail 31579 invoked by uid 89); 6 Apr 2013 09:49:49 -0000 X-Spam-SWARE-Status: No, score=-2.7 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KHOP_RCVD_TRUST,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,TW_BD autolearn=ham version=3.3.1 Received: from mail-we0-f171.google.com (HELO mail-we0-f171.google.com) (74.125.82.171) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Sat, 06 Apr 2013 09:49:46 +0000 Received: by mail-we0-f171.google.com with SMTP id d46so3468023wer.30 for ; Sat, 06 Apr 2013 02:49:44 -0700 (PDT) X-Received: by 10.180.87.193 with SMTP id ba1mr3420514wib.10.1365241784086; Sat, 06 Apr 2013 02:49:44 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.57.1 with HTTP; Sat, 6 Apr 2013 02:49:24 -0700 (PDT) From: Davide Pippa Date: Sat, 06 Apr 2013 09:49:00 -0000 Message-ID: To: ecos-discuss@sourceware.org Content-Type: text/plain; charset=ISO-8859-1 Subject: [ECOS] How to build an ecos application "redboot-aware" X-SW-Source: 2013-04/txt/msg00005.txt.bz2 Hi! I'm trying to use redboot with a TWR-K70F120M board. I've succeeded in doing the following: - got a rom with redboot compiled and running; - can connect to redboot console thru osbdm usb virtual serial port (using P&E micro terminal); - can connect to redboot console thru ethernet (I set the IP to 12.13.14.216 and connect to port 9000); Now I'm trying to use GDB to debug an application. I've tried with an application I used to work with (a simple demo blinking leds and sending udp packets), but I cannot successfully load it thru gdb, i see that: $ arm-eabi-gdb demo1.elf GNU gdb (eCos GNU Tools 4.6.3-20120623) 7.4.1 Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later 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=i686-pc-cygwin --target=arm-eabi". For bug reporting instructions, please see: ... Reading symbols from /cygdrive/h/Works/Arm/PyIde/proj/demo1/Debug/demo1.elf...do ne. (gdb) target remote 12.13.14.216:9000 Remote debugging using 12.13.14.216:9000 update_arp_entry (netif=0x0, ipaddr=0x0, ethaddr=0x0, flags=) at /cygdrive/h/Works/Arm/PyIde/build/ecos/packages/net/lwip_tcpip/current/sr c/netif/etharp.c:480 480 ip_addr_ismulticast(ipaddr)) { (gdb) load Loading section .rom_vectors, size 0x8 lma 0x0 Loading section .kinetis_misc, size 0x3b0 lma 0x8 Loading section .flash_conf, size 0x10 lma 0x400 Loading section .ARM.exidx, size 0x8 lma 0x410 Loading section .text, size 0x11f10 lma 0x418 Ignoring packet error, continuing... Ignoring packet error, continuing... Remote communication error. Target disconnected.: Connection reset by peer. (gdb) (gdb) I suppose some problem comes from the fact that this application was compiled to work "stand-alone", without any redboot support (I mean I used to download the image with openocd, without any redboot thing build and debugging with openocd only). What kind of configuration change should I do to make an application "redboot-aware"? Is there any of the available templates (for the TWR-K70F120M) already built for that? Or, can I start from the usual template (I use the lwip_eth template) and modify it to support redboot? Or am I missing something else? Thanks! Pyper -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss