public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org To: unassigned@bugs.ecos.sourceware.org Subject: [Bug 1001219] Ethernet driver for STM32 connectivity line with port on MMstm32f107 board. Date: Tue, 11 Oct 2011 21:08:00 -0000 [thread overview] Message-ID: <20111011210809.A3ED82F7800F@mail.ecoscentric.com> (raw) In-Reply-To: <bug-1001219-777@http.bugs.ecos.sourceware.org/> Please do not reply to this email. Use the web interface provided at: http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001219 --- Comment #12 from Ilija Kocho <ilijak@siva.com.mk> 2011-10-11 22:08:06 BST --- (In reply to comment #6) > Created an attachment (id=1395) --> (http://bugs.ecos.sourceware.org/attachment.cgi?id=1395) [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. 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. 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). 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. 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. Ilija -- Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
next prev parent reply other threads:[~2011-10-11 21:08 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-05-03 22:11 [Bug 1001219] New: " bugzilla-daemon 2011-05-04 7:41 ` [Bug 1001219] " bugzilla-daemon 2011-05-12 9:18 ` bugzilla-daemon 2011-10-08 14:02 ` bugzilla-daemon 2011-10-08 14:27 ` bugzilla-daemon 2011-10-10 20:51 ` bugzilla-daemon 2011-10-10 20:54 ` bugzilla-daemon 2011-10-10 20:56 ` bugzilla-daemon 2011-10-10 21:13 ` bugzilla-daemon 2011-10-10 21:50 ` bugzilla-daemon 2011-10-11 19:53 ` bugzilla-daemon 2011-10-11 20:39 ` bugzilla-daemon 2011-10-11 21:08 ` bugzilla-daemon [this message] 2011-10-11 21:45 ` bugzilla-daemon 2011-10-12 11:25 ` bugzilla-daemon 2011-10-12 20:34 ` bugzilla-daemon 2011-10-12 21:15 ` bugzilla-daemon 2011-10-16 14:12 ` bugzilla-daemon 2011-10-16 14:12 ` bugzilla-daemon
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20111011210809.A3ED82F7800F@mail.ecoscentric.com \ --to=bugzilla-daemon@bugs.ecos.sourceware.org \ --cc=unassigned@bugs.ecos.sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).