This is the mail archive of the
mailing list for the eCos project.
[Bug 1001219] Ethernet driver for STM32 connectivity line with port on MMstm32f107 board.
- From: bugzilla-daemon at bugs dot ecos dot sourceware dot org
- To: ecos-patches at ecos dot sourceware dot org
- Date: Tue, 11 Oct 2011 22:08:09 +0100
- Subject: [Bug 1001219] Ethernet driver for STM32 connectivity line with port on MMstm32f107 board.
- Auto-submitted: auto-generated
- References: <email@example.com/>
Please do not reply to this email. Use the web interface provided at:
--- Comment #12 from Ilija Kocho <firstname.lastname@example.org> 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.
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.