Anybody got any ideas about this latest RCW problem, here in this dead forum?

Comments

4 comments

  • Avatar
    Michael Johnson

    What's the problem?

    0
    Comment actions Permalink
  • Avatar
    Trahn Knee

    Michael,

    I was unable to compile STM32CubeMX for F4 or L1 devices, compiler detected errors in the CMSIS file. However, I installed RCW 3.6.5 onto a newer laptop and other than editor color scheme, left all the settings default, took the same files that were failing to compile on the other laptop and it compiles ok?  So I screwed up something. Now, I'll go back to the other laptop and compare the settings to see what I phk'd up. Heck, it only took about a month to figure it out. Tthanks for checking in to the 'community' and making comments. It is appreciated.

    walt

    retired control segment GPS engineer

    0
    Comment actions Permalink
  • Avatar
    Michael Johnson

    No problem - we're looking into another way to import Keil projects (.gpdsc files) so hopefully we'll get better in this area.

    0
    Comment actions Permalink
  • Avatar
    Tero Koskinen

    Try exporting the code as SW4STM32 project. It is ST's own IDE, which uses GCC.

    Once you have the code, don't import the SW4STM32 project itself, but instead create new Crossworks project for F4/L1, add all the required/generated source code files into the new Crossworks project and set the include paths.

     

    I use GCC (https://launchpad.net/gcc-arm-embedded) and cmake to build some F4/L4 projects created this way and it as worked so far pretty nicely. I haven't used Crossworks for this, but I don't see why it shouldn't work also.

    Yours,

     Tero

     

    0
    Comment actions Permalink

Please sign in to leave a comment.