knutolai

So I ran into some trouble with ODeV when writing a program where I combine C and C++. 

I keep getting "expected '=', ',', ';', 'asm' or '__attribute__' before '*' token" when building. ODeV does offer a C++ extension (FreeRTOS_EC) and there is a downloadable project for a STM32F1xx device using this extension (Cortex_STM32F1xx_CPP_Template).

I added FreeRTOS_EC as a Linked Resource in my project, but it didn't really do any difference. When further inspecting and comparing  the preferences of the I noticed that both projects used the same Tool Chain with the same Used Tools. However only the F1xx project has the C++ Compiler (ARM Sourcery Windows GCC C++ Compiler) listed in the Discovery Options Tools list. 

For some reason my project does not understand that it needs this compiler to build the code. 

I tried applying all available discovery profiles, but none of them adds the C++ Compiler to the tools list

Does anyone have any suggestions on other things I could try? 

 

[color=rgb(40,40,40);font-family:helvetica, arial, sans-serif;]OMG (sigh) yes I should have mentioned that, too; I forgot about the update tool version issue.  I know folks have had problems with the earlier version (and hence why Chris put a link to the working ones, because they are harder to find otherwise).  And I am apparently using 3.0.1 and 3.0.2 myself, according to the title bar text.[/color]

That did the trick! I imagined v. 3.0.0 was a stable working version (mostly because of the naming). 

Thank you very much for the help! Now I can finally start testing my code! 

 

[color=rgb(40,40,40);font-family:helvetica, arial, sans-serif;] (which is better than where you are now, right?  which is ground negative x?)[/color]

Haha yeah agreed. 

I found the .dfu in the thread. Thank you. Tried to flash it onto the board following the steps in the thread. I got the same result as stated above. I'm using version 3.0.0 of DFUSE. The thread asks for version 3.0.2 and 3.0.1. Could this be vital to how the program runs? 

I'm sure DFUSE and my computer recognizes that my Netduino 2 is in bootloader mode. The upgrade option in DFUSE Demonstrator is grayed out when I attach it while not pressing the reset button. I'm a bit vary of using the DFUSE tools in any other ways than suggested in the thread, but could I try the "Upload Action" pane in DFUSE Demonstrator? It lets me upload a .dfu file (instead of upgrading(?), a little confusing). I don't wanna reach a point of no return with my board 

[color=rgb(40,40,40);font-family:helvetica, arial, sans-serif;]Yes,you can use the elf file with GDB for debug.[/color]

Or you can use below command to generate .hex file for burning(using st-link utitily or something similar)

arm-none-eabi-objcopy.exe -O ihex Yourfilename.elf Yourfilename.hex

Great that worked alright. Again thank you so much for the link to ODeV! Amazing resource

 

[color=rgb(40,40,40);font-family:helvetica, arial, sans-serif;]*  is the DFU valid?  not only valid as a dfu, but when you built it, does it have what you think it does.[/color]

The .dfu file is generated from a .hex file, again generated from a .elf file I get when I build my project. 

 

[color=rgb(40,40,40);font-family:helvetica, arial, sans-serif;]*  did you first erase the device?  with the stdfu tester?[/color]

Yes I always erase the board using the steps in the provided link. I think the board-erasing-process is working as that actually takes a few seconds to complete. The tool also states something like "erasing complete/successful" so I'm fairly confident this step is done correctly. 

 

[color=rgb(40,40,40);font-family:helvetica, arial, sans-serif;]*  did you select the 'verify' option, so the that it will read back what you wrote? (this is particularly useful to make sure you didn't forget to first erase)[/color]

When I select 'Upgrade' I get "Target 00: Upgrade Successful" (after upgrade that takes 0 seconds to complete)
When I select 'Verify' I get "Target 00: "Verify Successful". Im not shown by DFUSE what was written to the device. 

 

[color=rgb(40,40,40);font-family:helvetica, arial, sans-serif;]Lastly (and I should have mentioned it firstly), try to flash the official firmware to verify your understanding of the flashing tool.  Then, if you have problems, you can be fairly confident that something is awry with the dfu itself (or with the contents therein).[/color]

Thats a great idea. I can't find the Netduino 2 firmware in a .dfu format. I found the firmware .zip file here: http://www.netduino.com/downloads/. I don't know how to use the content however as there is no README file provided. Could anyone supply me with either a firmware in the .dfu format or steps on how to generate it from the resources in the .zip file? 

[color=rgb(40,40,40);font-family:helvetica, arial, sans-serif;]What OS are you using?[/color]

IIRC, only some versions work on XP.

And, as always, run the program as admin if you're not already on an admin account.

I'm working in Windows 7 Home Premium. I'm the system admin.