LeafLabs Garden

A place to share, learn, and grow...

1. 

   soundcyst
   Member

   Has anyone done this / care to share?

   I'm about half-way there, and I can't figure out how to make IAR skip the .s files during the Compile stage and remember they're there in the Assembler stage.

   Googling didn't help, nor did consulting IAR's manuals..

   *edit* but it should have. There is a section in the manual that I had overlooked titled "Mixing C and assembler modules"... D'oh!

   The real problem is indicated in the post below.. (let this be another lesson to me: document symptoms, not guesses of their cause!)

   Posted 5 years ago #
2. 

   soundcyst
   Member

   Looking into this a little more, it seems like IAR might not actually be invoking the C compiler.. It is, however, erroring out quite a bit. Comparing the .s file provided from git to a .s startup file I'm using in a working project, the syntax at the beginning of the file looks a little different...

   the one IAR likes in my other projects:
   
MODULE ?cstartup

   ;; Forward declaration of sections.
   SECTION CSTACK:DATA:NOROOT(3)

   SECTION .intvec:CODE:NOROOT(2)

   EXTERN __iar_program_start
   EXTERN SystemInit
   PUBLIC __vector_table

   DATA

   __vector_table
DCD sfe(CSTACK)
DCD Reset_Handler ; Reset Handler
DCD NMI_Handler ; NMI Handler

   (etc. for the rest of the interrupt vector handlers)

   the one it doesn't like:
   
.syntax unified
.cpu cortex-m3
.fpu softvfp
.thumb

   .global g_pfnVectors
   .global SystemInit_ExtMemCtl_Dummy
   .global Default_Handler

   /* start address for the initialization values of the .data section.
defined in linker script */
.word _sidata


   for the first 5 lines, IAR gives "Bad instruction" errors, and then for on line 6, it gives a "Duplicate label:'.global'" error.

   then, pretty much every line gives either a bad instruction or duplicate label, or both.

   So does IAR have a different assembler syntax or something?

   Posted 5 years ago #
3. 

   x893
   Member

   Use startup_stm32f10x_md.s from any ST example and stm32f10x_flash.icf for build.
   May be need to change interrupt handlers name.
   STM32F10x_StdPeriph_Lib_V3.4.0 contain examples for many IDEs.

   Posted 5 years ago #
4. 

   soundcyst
   Member

   hmm.. time to brush up on my assembly.

   the reset routine in startup_stm32f10x is not the same as the maple reset routine, so i guess figuring that out is the next step.

   Posted 5 years ago #
5. 

   gbulmer
   Moderator

   soundcyst - maybe I am miss-understanding something ...

   Do you want to build the Maple boot loader, or do you want to build something with some bits of the Maple bootloader, and some bits of something else?

   If all you want is the Maple bootloader, I don't understand why it matters how IAR code works. I can imagine a problem is getting rid of all the IAR code.

   If you have time to explain, I'd like to understand what I am missing.

   Posted 5 years ago #
6. 

   soundcyst
   Member

   i want to build the maple bootloader for my STM3210E-EVAL board, so that I can get my feet wet with Maple's IDE and libraries. (yes, just using libmaple within an IAR project could work, but it makes any code I write not-very-portable to other maple users)

   the main issue is that GNU's assembler syntax (for directives and symbols) is different than IAR's.

   x893's suggestion was to use ST's provided startup.s files, which "work" in the sense that they build and do something. they just don't do the same thing as the maple startup file.

   the icf file is another issue that i'll have to deal with after i get the assembly squared away.

   Posted 5 years ago #
7. 

   gbulmer
   Moderator

   soundcyst - that is helpful.
   Is a reasonable summary "you'd like to make your STM3210E-EVAL operate like a Maple"?

   i want to build the maple bootloader for my STM3210E-EVAL board, so that I can get my feet wet with Maple's IDE and libraries.

   Okay, so I assume you know that the Maple bootloader can be built using the command line described here:
   http://leaflabs.com/docs/libmaple/unix-toolchain/

   This will generate a binary file which is the bootloader. I think that could be uploaded to your board.
   (That was partly for the benefit of future readers of this thread).

   So, what part of the process do you want or need to use IAR?

   Posted 5 years ago #
8. 

   soundcyst
   Member

   Is a reasonable summary "you'd like to make your STM3210E-EVAL operate like a Maple"?

   Quite.

   Unfortunately the unix toolchain tutorial is distinctly lacking in Cygwin/MinGW information. I did find a thread on the forum discussing the topic, but I didn't really get anywhere with it, possibly because my MinGW install is not complete (?) -- I think GitBash installed it, and don't recall if it did so completely or bare-minimum-ly.

   I've been trying to do this in my downtime at work, which has been sporadic, and prone to distractions.

   I'm not sure if I'll complete the task anytime soon, since a rev5 should be on its way to me soon =)

   If that board finds itself a permanent home before more boards are available, I may come back to the drawing board on this one.

   Posted 5 years ago #
9. 

   gbulmer
   Moderator

   Ah, I think I've got it! The nub of the problem is trying to use Cygwin/MinGW to build on Windows.

   Thanks for taking the time to explain.

   I accept this is even more work, but it's probably worth saying rather than assuming ...
   Have you considered using VirtualBox to get off the ground?
   Run that on Windows to get a *NIX system up, then use that to build a bootloader.

   Posted 5 years ago #
10. 

    mbolivar
    LeafLabs

    soundcyst,

    if it's just a matter of having a copy of the compiled maple bootloader, we host them here:

    http://static.leaflabs.com/pub/leaflabs/maple-bootloader/

    Posted 5 years ago #
11. 

    soundcyst
    Member

    i suppose i can give that a try. i'll have to double check the memory maps though, as the chip on the eval board is a stm32f103zet6

    Posted 5 years ago #
12. 

    mbolivar
    LeafLabs

    i see. then yes, you might need to make some changes.

    just fyi, you can check out the differences between the master and mini-boot branches of the maple-bootloader github repo to get some idea of what you might have to tweak to get it working on your chip:

    https://github.com/leaflabs/maple-bootloader/compare/master...mini-boot

    Posted 5 years ago #

RSS feed for this topic

Reply

You must log in to post.