LeafLabs Garden » Topic: Upload user code with USART

LeafLabs Garden » Topic: Upload user code with USART http://forums.leaflabs.com/topic.php?id=1311 A place to share, learn, and grow... en-US Fri, 22 Jan 2016 00:17:48 +0000 http://bbpress.org/?v=1.0.2 <![CDATA[Search]]> q http://forums.leaflabs.com/search.php gbulmer on "Upload user code with USART" http://forums.leaflabs.com/topic.php?id=1311#post-8139 Wed, 08 Feb 2012 12:24:55 +0000 gbulmer 8139@http://forums.leaflabs.com/ djk - objdump can be used in a simple way: arm-none-eabi-objdump -d foo.elf It has lots of options, but you can ignore most of them. djk on "Upload user code with USART" http://forums.leaflabs.com/topic.php?id=1311#post-8136 Wed, 08 Feb 2012 09:52:40 +0000 djk 8136@http://forums.leaflabs.com/ 1. Great news on the windows 7. I am going to test and document this and post howto & results i a new thread when i'm done. 2-3. yes so what i'm looking for is a a text file listing the memory locations for each bit of code in codespace, variable in the dataspace etc. Probably most IDE's or makefiles i've worked with in the past had this text dump built in to the build process. I will do my homework on OBJDUMP, sounds like i can get what i need that way. Thanks again! gbulmer on "Upload user code with USART" http://forums.leaflabs.com/topic.php?id=1311#post-8123 Wed, 08 Feb 2012 06:12:29 +0000 gbulmer 8123@http://forums.leaflabs.com/ djk - <blockquote>1. I suppose this could be good news for those of us on Windows 7 and all the issues with the DFU and comms drivers? can we flash over UART1? (i'm thinking FTDI or bluetooth). </blockquote> Yes, absolutely. You'll need one of the upload utilities; on Windows ST provides one. Google thinks it is here somewhere: <a href="http://www.st.com/internet/mcu/product/221020.jsp" rel="nofollow">http://www.st.com/internet/mcu/product/221020.jsp</a> You might consider spending the extra money to get an ST-LINK/V2: <a href="http://www.st.com/internet/evalboard/product/251168.jsp" rel="nofollow">http://www.st.com/internet/evalboard/product/251168.jsp</a> This has upload etc. support on Windows. With suitable gdbserver software, It can also be used with gdb to give hardware debugging (breakpoints, datawatch, single step, etc) It is $25 from Future <a href="http://www.futureelectronics.com/en/technologies/development-tools/development-tool-hardware/Pages/3008294-ST-LINK-V2.aspx?IM=0" rel="nofollow">http://www.futureelectronics.com/en/technologies/development-tools/development-tool-hardware/Pages/3008294-ST-LINK-V2.aspx?IM=0</a> <blockquote>2. i hope this isn't too much of a newb question....where can i find a code space memory map for the maple? i've had a tough time looking through documentation on this trying to stay out of the code. </blockquote> Not sure what you mean. There is a Maple bootloader at the start of flash, then the user program. There are linker scripts (*.ld) which define the memory layout. For example: <pre><code>/* * Maple (STM32F103RBT6, medium density) linker script for Flash builds. */ /* * Define memory spaces. */ MEMORY { ram (rwx) : ORIGIN = 0x20000C00, LENGTH = 17K rom (rx) : ORIGIN = 0x08005000, LENGTH = 108K } /* * Use medium density device vector table */ GROUP(libcs3_stm32_med_density.a) REGION_ALIAS("REGION_TEXT", rom); REGION_ALIAS("REGION_DATA", ram); REGION_ALIAS("REGION_BSS", ram); REGION_ALIAS("REGION_RODATA", rom); /* * Define the rest of the sections */ _FLASH_BUILD = 1; INCLUDE common.inc</code></pre> You can see where the Maple program is loaded in Flash (starting at 0x08005000), and what part of RAM it can use. <blockquote>3. related to the last quesiton i've tracked down the .elf files in the user data temp directories but not made much the effort to capture and get an elf file reader. Any recommendations for windows elf readers? ... </blockquote> Not sure exactly what you mean by "elf readers". I assume you want something which prints some kind of memory map of a program? Somewhere in your Maple installation, you should be able to find objdump. On the Mac it is MapleIDE.app/Contents/Resources/Java/hardware/tools/arm/arm-none-eabi/bin/objdump and (the long "arm-none-eabi..." name avoids confusion in a cross compilation environment): MapleIDE.app/Contents/Resources/Java/hardware/tools/arm/bin/arm-none-eabi-objdump there is a manual for the "Binary Utilities" at: <a href="https://sourcery.mentor.com/sgpp/lite/arm/portal/release1802" rel="nofollow">https://sourcery.mentor.com/sgpp/lite/arm/portal/release1802</a> which explains all of the options. It will disassemble the program, and print an address map. djk on "Upload user code with USART" http://forums.leaflabs.com/topic.php?id=1311#post-8117 Tue, 07 Feb 2012 22:13:02 +0000 djk 8117@http://forums.leaflabs.com/ 1. I suppose this could be good news for those of us on Windows 7 and all the issues with the DFU and comms drivers? can we flash over UART1? (i'm thinking FTDI or bluetooth). 2. i hope this isn't too much of a newb question....where can i find a code space memory map for the maple? i've had a tough time looking through documentation on this trying to stay out of the code. 3. related to the last quesiton i've tracked down the .elf files in the user data temp directories but not made much the effort to capture and get an elf file reader. Any recommendations for windows elf readers? And any way to direct the IDE to put the elf (or some memory map file) in your sketch folder? Thanks! Abo on "Upload user code with USART" http://forums.leaflabs.com/topic.php?id=1311#post-8046 Fri, 03 Feb 2012 11:02:47 +0000 Abo 8046@http://forums.leaflabs.com/ Thank you all, I got it to boot-load + upload my new code via USART with STMFlashLoader. Indeed the behavior of STMFlashLoader are similar to the Python script... perhaps there is a 'erase all' command in the Python script that pevented me from uploading the two .bin? (bootload.bin + usercode.bin) gbulmer on "Upload user code with USART" http://forums.leaflabs.com/topic.php?id=1311#post-7988 Wed, 01 Feb 2012 20:48:21 +0000 gbulmer 7988@http://forums.leaflabs.com/ ala42 - I'm not a Windows user, but if Abo is, it might be better than the Python script. ala42 on "Upload user code with USART" http://forums.leaflabs.com/topic.php?id=1311#post-7987 Wed, 01 Feb 2012 20:10:31 +0000 ala42 7987@http://forums.leaflabs.com/ The package also includes the STMFlashLoader.exe command line tool. gbulmer on "Upload user code with USART" http://forums.leaflabs.com/topic.php?id=1311#post-7985 Wed, 01 Feb 2012 19:36:08 +0000 gbulmer 7985@http://forums.leaflabs.com/ ala42 - thank you, I've never used that tool. That will save a lot of effort. ala42 on "Upload user code with USART" http://forums.leaflabs.com/topic.php?id=1311#post-7983 Wed, 01 Feb 2012 18:58:09 +0000 ala42 7983@http://forums.leaflabs.com/ There is absolutely no problem when you use the STM "Flash Loader Demo" tool to flash the bootloader once to $8000000 and later use the STM "Flash Loader Demo" tool to upload your maple build program to $8005000. The only thing you have to take care of is that you do not erase the complete flash rom, you must just set the checkbox to erase only the used pages. gbulmer on "Upload user code with USART" http://forums.leaflabs.com/topic.php?id=1311#post-7979 Wed, 01 Feb 2012 15:38:02 +0000 gbulmer 7979@http://forums.leaflabs.com/ Abo <blockquote>So I guess my question should change from "uploading user code (the .bin file)" to "writing self contained STM32F".</blockquote> Yes, exactly. <blockquote>My understanding is that the normal flashing procedure with Maple IDE is 1. USART bootloader flashes the Maple bootloader, a self-contain program via USART (run in python) 2. Maple bootloader flashes the user program, not a self-contain program via USB (run with dfu-util).</blockquote> Yes. <blockquote>The combine bootloader.bin file + user code.bin file + some work by the Maple IDE (or dfu-util), create a self-contain firmware.</blockquote> Sort of yes. The bootloader.bin is permanently on the board, and creates the environment for the uploaded user code.bin. <blockquote>I guess the goal I need to achieve would be 1. USART bootloader flashes the user program, a self-contain program via USART (run in python)</blockquote> Yes, with a broken USB that is exactly what you need. There are several other USART uploaders that run on the host PC. I think I saw a list at PyMite or an associated web site. <blockquote>From the look of the python code, it feels like I can upload a .bin file to any memory location I want.</blockquote> Not quite. There has to be values for the reset vector, which is, by default at 0x00000000. Combinations of the BOOT pins will give three options for its location (See RM0008, section 3.4 "Boot configuration"). There are a few other vectors which should be initialised. Once that is set up, yes, the program can be anywhere in valid flash or RAM. <blockquote>Would it be possible to modify the wirish.c init() function so that the compiled .bin file become a self-contained STM32 program?</blockquote> Where is wirish.c? I thought that had been changed. Do you mean boards.cpp? I am working through the same question. Essentially - interrupt vectors need to be set up in the NVIC vector table, - reset handler (and preferably a default handler for faults and interrupts) Then execution of the reset handler runs (or calls) code for: - initialised variables need to be initialised (by copying from a segment in flash) - uninitialised variables need to be zero'd - system and peripheral clocks, flash and NVIC - static class initialisers, - systick timer, and other peripherals I am 98% certain there is startup code (cs3) that comes with CodeSourcery lite that covers the first 4 steps. That source isn't included in the Maple distribution, and it might be that the license doesn't allow LeafLabs to include it. Depending on what you need to do, for example if USB is not needed, then the cs3 code might be everything. ST Micro also supply all the code needed for setup. It is a bit ugly, mostly in assembler, which is not necessary. Cortex-M3 functions can be called with nothing more than a stack pointer set, and a starting address. (full disclosure: I am not a member of LeafLabs staff.) Abo on "Upload user code with USART" http://forums.leaflabs.com/topic.php?id=1311#post-7972 Tue, 31 Jan 2012 19:23:35 +0000 Abo 7972@http://forums.leaflabs.com/ Thanks gbulmer, while I have some C experience, I not experience in the inner work of MapleIDE and ST MCU... So I guess my question should change from "uploading user code (the .bin file)" to "writing self contained STM32F". My understanding is that the normal flashing procedure with Maple IDE is 1. USART bootloader flashes the Maple bootloader, a self-contain program via USART (run in python) 2. Maple bootloader flashes the user program, not a self-contain program via USB (run with dfu-util). The combine bootloader.bin file + user code.bin file + some work by the Maple IDE (or dfu-util), create a self-contain firmware. I guess the goal I need to achieve would be 1. USART bootloader flashes the user program, a self-contain program via USART (run in python) From the look of the python code, it feels like I can upload a .bin file to any memory location I want. My problem is then writing a self-contain program without MapleIDE and dfu-util. Would it be possible to modify the wirish.c init() function so that the compiled .bin file become a self-contained STM32 program? It feels like the IDE generated main() is only missing a few calls to become self-contain. Compare the code of the bootloader main (which is a self-containted program) and the wirish.c init(), there are a lot of overlaps such as setting the clock, setupUSB, etc etc. What it missing in the wirish that pevent it from being self-contain? many thanks~ gbulmer on "Upload user code with USART" http://forums.leaflabs.com/topic.php?id=1311#post-7967 Tue, 31 Jan 2012 14:18:16 +0000 gbulmer 7967@http://forums.leaflabs.com/ Abo - USART upload is manufactured into the chip by ST Micro. The USB bootloader is a separate and independent program uploaded by LeafLabs into Maple. They are both on chip, but do not collaborate. There is the Application note "AN3155" at st.com called "USART protocol used in the STM32TM bootloader" which explains how the USART upload works. That USART bootloader doesn't know anything about the Maple bootloader which is added by LeafLabs. The USART bootloader is really designed to load the main, and only, program into the chip. It doesn't know anything about the Maple bootloader, so it might even erase everything (I have not checked). Further, the Maple bootloader will not know anything about a program loaded by USART bootloader, so things might not be set up correctly for it to work even if the USB bootloader isn't erased. Finally, LeafLab' Maple IDE does not generate self contained STM32F program, so even if you loaded it correctly, overwriting the Maple bootloader, it would very likely not work correctly. (full disclosure: I am not a member of LeafLabs staff.) Abo on "Upload user code with USART" http://forums.leaflabs.com/topic.php?id=1311#post-7965 Tue, 31 Jan 2012 13:42:48 +0000 Abo 7965@http://forums.leaflabs.com/ I'm current trying to figure out how to upload user program (using the .bin file in the 'Temp' folder created by MapleIDE) by the USART port. I got a maple that has a damaged USB port. So I wonder if I can upload my bin by USART, just like how we can upload bootloader by USART. I look into the python code and change the address from 0x8000000 to 0x8005000 (user code starts at 0x8005000?) I first upload the boot loader to address 0x8000000 using the python script. Things works great. Then I upload my user code to address 0x8005000 and seems crush things (normally uploading via USB will first reset the chip, LED flash a few times, then go to user code - that didn't happen) I wonder if there's guide line on uploading user code (the .bin file) via USART? Many thanks