http://forums.leaflabs.com/topic.php?id=13447 A place to share, learn, and grow... en-US Fri, 22 Jan 2016 00:19:01 +0000 http://bbpress.org/?v=1.0.2 q http://forums.leaflabs.com/search.php http://forums.leaflabs.com/topic.php?id=13447&page=3#post-105032 Sat, 07 Dec 2013 17:04:26 +0000 fma 105032@http://forums.leaflabs.com/ <p>Thanks for all these links!</p> <p>As far as I understand, when compiling code under maple-ide, the resulting code does not have enough things to work: it is designed to work in conjonction with the bootloader, which makes some work before (system clock and so). Am I right?</p> <p>If so, as you said, I will have to dig into the bootloader, and maybe adapt one for my board (which is a simple STM32F103VBT6).</p> <p>But my final goal is to make a new firmware for a vent. unit (using that chip). and this vent. unit does not have the usb lines out. I can only upload a firmware using the stm32 internal bootloader (as I'm trying to do with my dev board), or via JTAG. This means that I will have to do all the init stuff myself :o/</p> <p>Maybe using maple-ide is not the best way to achieve this goal? Should I use other libs? </p> http://forums.leaflabs.com/topic.php?id=13447&page=3#post-105030 Sat, 07 Dec 2013 15:00:51 +0000 gbulmer 105030@http://forums.leaflabs.com/ <p>fma - <em>"So, I don't have any bootloader on it, and I'm not using DFU; I switch to the internal st bootloader, and upload code through USART1..."</em></p> <p>Okay, got it.</p> <p><em>"I'm new to stm32 dev, so I don't know yet how things work at boot. Is there a usefull documentation I can read?"</em><br /> What sort of thing do you want to know?<br /> If you can outline your 'use-case' (i.e. what you're trying to achieve), we might be able to offer better help.</p> <p>There are a few things you could read.<br /> There is a pretty useful book for Cortex-M3:<br /> <a href="https://www.elsevier.com/books/the-definitive-guide-to-the-arm-cortex-m3/yiu/978-1-85617-963-8" rel="nofollow">https://www.elsevier.com/books/the-definitive-guide-to-the-arm-cortex-m3/yiu/978-1-85617-963-8</a><br /> This covers quite a lot abut the Cortex-M3 processor, and using different development tools.</p> <p>It might be worth getting copies of the Cortex-M3 manuals from ARM:<br /> <a href="http://infocenter.arm.com/help/index.jsp" rel="nofollow">http://infocenter.arm.com/help/index.jsp</a><br /> or ST</p> <p>However, most of the startup work is setting up peripherals and the interrupt vectors.<br /> The initial startup is in the bootloader, which makes it a bit awkward to follow.</p> <p>Then the peripherals are described in detail in RM0008 (you probably have that):<br /> <a href="http://www.st.com/st-web-ui/static/active/en/resource/technical/document/reference_manual/CD00171190.pdf" rel="nofollow">http://www.st.com/st-web-ui/static/active/en/resource/technical/document/reference_manual/CD00171190.pdf</a></p> <p>So looking at the start-up code, armed with RM0008 is probably helpful if that is the area you want to understand.</p> <p>If, on the other hand, you want to understand more about start-up, then either dig through the Maple bootloader, or look at ST's standard peripheral library downloaded from:<br /> <a href="http://www.st.com/web/en/catalog/tools/PF257890#" rel="nofollow">http://www.st.com/web/en/catalog/tools/PF257890#</a></p> <p>It has example startup code for several different IDEs. </p> http://forums.leaflabs.com/topic.php?id=13447&page=3#post-105028 Sat, 07 Dec 2013 13:20:48 +0000 fma 105028@http://forums.leaflabs.com/ <p>Thanks for you answer.</p> <p>I'm using a non-officially supported board, for which I added support (see the begining of this thread). So, I don't have any bootloader on it, and I'm not using DFU; I switch to the internal st bootloader, and upload code through USART1...</p> <p>I'm new to stm32 dev, so I don't know yet how things work at boot. Is there a usefull documentation I can read? </p> http://forums.leaflabs.com/topic.php?id=13447&page=3#post-105027 Sat, 07 Dec 2013 12:31:20 +0000 gbulmer 105027@http://forums.leaflabs.com/ <p>fma - The page<br /> <a href="http://leaflabs.com/docs/unix-toolchain.html" rel="nofollow">http://leaflabs.com/docs/unix-toolchain.html</a><br /> Shows programs being loaded using the dfu-util:</p> <pre><code>Found DFU: [0x1eaf:0x0003] devnum=0, cfg=0, intf=0, alt=0, name=&quot;DFU Program RAM 0x20000C00&quot; Found DFU: [0x1eaf:0x0003] devnum=0, cfg=0, intf=0, alt=1, name=&quot;DFU Program FLASH 0x08005000&quot;</code></pre> <p>I do believe the bootloader lives below 0x08005000</p> <p>Address 0x0 contains the 'top-of-stack' value, i.e. the initial stack pointer value (see RM0008 3.4 "Boot configuration"<br /> It isn't the value which the CPU uses as a code vector. </p> <p>Which board have you got? Does the board do anything? If you power up, or press reset does anything happen?</p> <p>(ful disclosure: I am not a member of LeafLabs staff.) </p> http://forums.leaflabs.com/topic.php?id=13447&page=3#post-105024 Sat, 07 Dec 2013 04:33:49 +0000 fma 105024@http://forums.leaflabs.com/ <p>Sorry to dig that old post...</p> <p>I finally received my dev. board, and I'm trying to make a simple blink example. Of course, it does not work. As there are a lot of things which can go wrong, I will try to check them one at a time.</p> <p>Once my example is compiled in maple-ide, I use stm32flash to download the resulting .bin file to the board, using the included bootloader (BOOT0=0, BOOT1=1). Then, I have to start the firmware. I assumed it is located at byte 0x0, but is it true? maple generated code is intended to work when a bootloader is on the flash, so I maye have to jump to another locate than 0x0...</p> <p>Any idea? </p> http://forums.leaflabs.com/topic.php?id=13447&page=2#post-29507 Mon, 09 Sep 2013 01:45:22 +0000 fma 29507@http://forums.leaflabs.com/ <p>Thanks! </p> http://forums.leaflabs.com/topic.php?id=13447&page=2#post-29463 Sat, 07 Sep 2013 09:42:56 +0000 ala42 29463@http://forums.leaflabs.com/ <p>That should be fine. </p> http://forums.leaflabs.com/topic.php?id=13447&page=2#post-29063 Fri, 06 Sep 2013 08:16:17 +0000 fma 29063@http://forums.leaflabs.com/ <p>As my board uses a 12MHz quartz, do you confirm that I only have to change this line:</p> <p>rcc_clk_init(RCC_CLKSRC_PLL, RCC_PLLSRC_HSE, RCC_PLLMUL_9);</p> <p>in the board.cpp file? In my case, I should use:</p> <p>rcc_clk_init(RCC_CLKSRC_PLL, RCC_PLLSRC_HSE, RCC_PLLMUL_6);</p> <p>Am I right? </p> http://forums.leaflabs.com/topic.php?id=13447&page=2#post-28607 Thu, 29 Aug 2013 10:13:15 +0000 fma 28607@http://forums.leaflabs.com/ <p>Well, my first goal is to have something working, but if I can do something clean, which can be used by others, or, better, merged in Maple official IDE, why not?</p> <p>What pre-processor macro name are you talking about? Something like MCU_xxx ? Or the STM32_MEDIUM/HIGH_xxx macro? I already added a new MCU_xxx var...</p> <p>I'm not sure to understand what you mean by "copy the GPIO E definition into that". Do you suggest to add other gpio.xx files, to add missing definitions (there are also things to do in rcc.h), or to patch these files, and use the new STM32_xxx macro (something between MEDIUM and HIGH)?</p> <p>It looks like there are a many place to change/patch things. Maybe the code would need some refactoring to allow a better integration of new boards/procs (in fact, it is already nicely written, and would only need a few modifications. But I think it should be done by main dev. team...). </p> http://forums.leaflabs.com/topic.php?id=13447&page=2#post-28602 Thu, 29 Aug 2013 07:19:13 +0000 gbulmer 28602@http://forums.leaflabs.com/ <p>fma - If you are planning on making it a properly supported board, I take back my suggestion of just moving the GPIO E definition.<br /> I had assumed, because the thread is called "unsupported boards" you wanted to get things working first. My mistake, sorry.</p> <p>For a properly supported board, you'll need to create another pre-processor macro name to test (with #ifdef), and wrap your source code changes in that. So copy the GPIO E definition into that, don't just move it. You'll also need board files, etc.</p> <p>IMHO, if the board is clearly marked "LC Studio" and a name, use those.</p> <p>(Full disclosure: I am not a member of LeafLabs staff) </p> http://forums.leaflabs.com/topic.php?id=13447&page=2#post-28596 Thu, 29 Aug 2013 01:37:03 +0000 fma 28596@http://forums.leaflabs.com/ <p>One more question: how should I name this dev board in Maple-IDE?</p> <p>It seems to be developed by LC STUDIO. As they have other boards, which may be added too in Maple-IDE, I would like to use a good naming convention, allowing extensions.</p> <p>What do you suggest has brand/model names? </p> http://forums.leaflabs.com/topic.php?id=13447&page=2#post-28595 Thu, 29 Aug 2013 00:31:32 +0000 fma 28595@http://forums.leaflabs.com/ <p>Ok.</p> <p>Thanks for your help, guys :o) </p> http://forums.leaflabs.com/topic.php?id=13447&page=2#post-28593 Wed, 28 Aug 2013 17:37:10 +0000 gbulmer 28593@http://forums.leaflabs.com/ <p>fma - I'd move the existing GPIO E definition. </p> http://forums.leaflabs.com/topic.php?id=13447&page=2#post-28589 Wed, 28 Aug 2013 12:45:49 +0000 fma 28589@http://forums.leaflabs.com/ <p>Mmm, after verification, it appears that the STM32F103VB (LQFP100) chip has a GPIO E port.</p> <p>But in Maple IDE, when using medium-density flag, I only get GPIO A to GPIO D...</p> <p>Should I hack the the code where GPIO E is defined, and moved it to the medium-density part? Or is there a better way? </p> http://forums.leaflabs.com/topic.php?id=13447&page=2#post-28588 Wed, 28 Aug 2013 12:40:17 +0000 gbulmer 28588@http://forums.leaflabs.com/ <p>fma - IMHO, it is frustratingly easy to make that mistake. I hope you didn't waste too much time.</p> <p>I have sent feedback to ST on that page today:<br /> <a href="http://www.st.com/web/en/catalog/mmc/FM141/SC1169/SS1031/LN1565" rel="nofollow">http://www.st.com/web/en/catalog/mmc/FM141/SC1169/SS1031/LN1565</a></p> <p>suggesting they highlight the different families, and ideally show how they are different using a similar style to:<br /> <a href="http://www.st.com/web/en/catalog/mmc/FM141/SC1169/SS1031" rel="nofollow">http://www.st.com/web/en/catalog/mmc/FM141/SC1169/SS1031</a><br /> but with the number of each peripheral too.</p> <p>If anyone has the energy, and thinks it might make a difference, please feedback too :-) </p>