From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2603 invoked by alias); 12 Oct 2011 11:25:07 -0000 Received: (qmail 2513 invoked by uid 22791); 12 Oct 2011 11:25:04 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from hagrid.ecoscentric.com (HELO mail.ecoscentric.com) (212.13.207.197) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 12 Oct 2011 11:24:46 +0000 Received: from localhost (hagrid.ecoscentric.com [127.0.0.1]) by mail.ecoscentric.com (Postfix) with ESMTP id 560822F78012 for ; Wed, 12 Oct 2011 12:24:45 +0100 (BST) Received: from mail.ecoscentric.com ([127.0.0.1]) by localhost (hagrid.ecoscentric.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1GPXzVtkpajh; Wed, 12 Oct 2011 12:24:43 +0100 (BST) From: bugzilla-daemon@bugs.ecos.sourceware.org To: ecos-patches@ecos.sourceware.org Subject: [Bug 1001219] Ethernet driver for STM32 connectivity line with port on MMstm32f107 board. X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: eCos X-Bugzilla-Component: Patches and contributions X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: jerzdy@gmail.com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: low X-Bugzilla-Assigned-To: unassigned@bugs.ecos.sourceware.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: In-Reply-To: References: X-Bugzilla-URL: http://bugs.ecos.sourceware.org/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Date: Wed, 12 Oct 2011 11:25:00 -0000 Message-Id: <20111012112443.CC1982F78001@mail.ecoscentric.com> Mailing-List: contact ecos-patches-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: ecos-patches-owner@ecos.sourceware.org X-SW-Source: 2011-10/txt/msg00023.txt.bz2 Please do not reply to this email. Use the web interface provided at: http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001219 --- Comment #14 from Jerzy Dyrda 2011-10-12 12:24:35 BST --- Hello Ilija, (In reply to comment #12) > (In reply to comment #6) > > Created an attachment (id=1395) --> (http://bugs.ecos.sourceware.org/attachment.cgi?id=1395) [details] [details] > > Platform for Propox MMstm32f107 module > > First to remind you to my remark in comment #4 > > At present the user will see F103ZE which is unlikely to be the target device. Please consider that such situation will always happen if further target will be introduced. > Platform may require the "STM variany in use" (CYGHWR_HAL_CORTEXM_STM32) to be > a specific device, or a set of eligible devices. If you opt for second case > just make sure that configtool resolves with the one found on Propox board. IMHO Either platform should provide proper STM32 variant or this option should be remove - nobody is interested in this option. Please review this option considering targets existing STM32F100/1/2/3 further like my STM32F105/7 and possible STM32F2xx, STM32F4xx and give me "order" how I should introduce STM32F105/7 family. > Why JTAG startup? AFAIK Connectivity line desn't feature FSMC (or am I out of > date?). I guess SRAM startup should work (but test it first). You are absolute right. JTAG startup doesn't have sens and I remove it. > Regarding ROM startup there's one issue: RAM region is required in order to > build RedBoot. True, there's not much use of RedBoot on device with 64KiB RAM > but somebody would like to try. Solution is simple rename SRAM region (nor > section) into RAM. I follow other cortex-m target like lm3s where is: - only one startup ROM - only SRAM section BTW. I've built RedBoot successful with only SRAM section. If it's possible I would like to shrink amount of startups only to ROM. > > Last but not least, please spend some time on Copyright banners > (all files that need it). > They should for instance show correct year, author/contributor, etc. Of course I correct it. Best regards, jerzy -- Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.