From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 122169 invoked by alias); 3 Mar 2019 17:38:30 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 122156 invoked by uid 89); 3 Mar 2019 17:38:29 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-6.9 required=5.0 tests=BAYES_00,GIT_PATCH_2,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=hitting, contacting, H*r:0800, our X-HELO: quarantine.blueorigin.com Received: from firewall.blueorigin.com (HELO quarantine.blueorigin.com) (72.165.233.66) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sun, 03 Mar 2019 17:38:28 +0000 Received: from pps.filterd (quarantine.blueorigin.com [127.0.0.1]) by quarantine.blueorigin.com (8.16.0.27/8.16.0.27) with SMTP id x23HcPrk006589 for ; Sun, 3 Mar 2019 09:38:25 -0800 Received: from mail02.blueorigin.com (MAIL02.blueorigin.com [10.1.1.46]) by quarantine.blueorigin.com with ESMTP id 2qytavrn1r-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT) for ; Sun, 03 Mar 2019 09:38:20 -0800 Received: from MAIL01.blueorigin.com (10.1.1.45) by MAIL02.blueorigin.com (10.1.1.46) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Sun, 3 Mar 2019 09:38:20 -0800 Received: from MAIL01.blueorigin.com ([fe80::38ac:bda:468a:aa3f]) by MAIL01.blueorigin.com ([fe80::38ac:bda:468a:aa3f%21]) with mapi id 15.00.1395.000; Sun, 3 Mar 2019 09:38:20 -0800 From: Jeff Wandling To: "gdb@sourceware.org" Subject: RE: [EXTERNAL] Re: Debugging big-endian ARM target from little-endian host Date: Sun, 03 Mar 2019 17:38:00 -0000 Message-ID: <0ca588ff4c074c5e99784c21d5326d19@MAIL01.blueorigin.com> References: <0338ed2b221c8a9e40d41037a66d847e@polymtl.ca> <672b1bfc87164c27a6a3e655eec6d813@MAIL01.blueorigin.com> <1222341d5bd82992b2cc14a451d5904a@polymtl.ca> <0d0fafabebda4de28cd415f0a9b5d7ce@MAIL01.blueorigin.com> <29e028e71ea334d4b74553ff8c704691@polymtl.ca> In-Reply-To: <29e028e71ea334d4b74553ff8c704691@polymtl.ca> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-SW-Source: 2019-03/txt/msg00007.txt.bz2 Likewise here. I regressed the JLinkGDBServer implementation, by going to = previous versions and found there are older releases that operate correctly= -- translating and transmitting endianness correctly. We're good here.. debugging the target is resolved. Thanks for the insigh= ts. To review for sake of those hitting the same issue: We're using the latest (8.2) GNU compiler and GDB tool chain. Our target is a big-endian (preferred) MCU, TMS570LC4357. The host is a little endian Linux box (Ubuntu 16.04). The debugger was the J-Link dongol from Segger. The JLink software package version was 6.42 (whatever was latest around Feb= -2019) The perceived issue was that the host, with the latest JLinkGDBServer packa= ge from Segger was not correctly transmitting/transforming the endianness, = the result was the gdb session would fail to handle commands due to the add= resses being wrong endianness. The fix was to go back and use an older JLinkGDBServer. I opted for 6.22 (= or there about) -----Original Message----- From: Simon Marchi =20 Sent: Saturday, March 2, 2019 5:48 PM To: Jeff Wandling Cc: gdb@sourceware.org Subject: Re: [EXTERNAL] Re: Debugging big-endian ARM target from little-end= ian host On 2019-03-01 17:15, Jeff Wandling wrote: > Yes, I am using -endian big with JLinkGDBServer Ok. I tested remote-debugging a big-endian machine (gcc110.fsffrance.org) to se= e how registers are actually transmitted. I confirm that they are transmit= ted in big endian form. This would mean that JLinkGdbServer is indeed at f= ault. I would suggest contacting Segger's support at this point. Simon