8 years, 1 month ago.

Hello Shiv.

1) Would you share the exact location of the Blink_Color_LED program that you imported ?

2) Be sure that you are also using the latest mbed library by selecting the mbed label in your project tree -> right mouse-click and then Update (see right side of your IDE / compiler screen).

3) If the project is not native to your target board then you must manually change the port pins for the color LED to suit the program logic. That is, different target boards have different free port pins and even more confusing, different port labels.

4) Did you add an external color LED to this target board or is it onboard from the factory ? We may have the same board in the lab so can confirm upon request.

5) Your observation is correct in that after you drag & drop the compiled binary onto the MBED drive letter - the onboard LED will flash for a few second to digest and flash your code into the local CPU's memory. After this task is completed the flashing will halt and often will self-boot on its own to run your saved program. You should not have to manually reset the board but does not hurt. After this reflashing of the memory, the program does get removed from the MBED drive letter.

To clarify this detail - even though the program (binary) is not visible on the drive letter, the saved program is in flash and will auto-run upon each CPU reset. Proceed to repeat this code development -> compile -> save -> test cycle till you are happy with your program.

Suggest you test your project as follows:

a) import the very basic LED flasher program from here:

https://developer.mbed.org/teams/mbed/code/mbed_blinky/

Select the BLUE import box on the right side of the screen after landing on the above webpage.

b) the above LED blinky is using LED1 reference which is common to all MBED enabled target boards which makes your testing a bit easier to get started

c) be sure to update the mbed library on the project tree else you will have a static and perhaps out-dated mbed library linked to your project and often can break the program

Please test and report your results.

Kumar

--

Shiv - do you have the following add-on board for your Nucleo board ? The RGB led is onboard this add-on shield.

https://developer.mbed.org/components/mbed-Application-Shield/

Also, you created a fresh project and imported the blinky LED program and compiled the source code but it fails to blink the LED ?

Can you post the source code ? Be sure to use the '<<code>>' before your code and then '<</code>>' after your code so that the posted format is easy to read. See the Editing tips on the bottom right of the text box where you post your updates on this forum.

-

Hey Shiv. What is the exact filename of your compiled binary ? I recall some similar issues when we were using the same tools a few months ago and the solution was to watch your filenames. Try to name something simple like:

blink.bin ; as the target file as an example

Otherwise, review the latest update to reflash your target board for MBED use. We have not had to do this but pretty sure the details are around to allow for a fresh start.

Also, the blink.bin remains compatible for use on the target board using only the ST tools. Let me check around once we reach the office on the proper links. That is, the bin file is able to stand alone.

#include "mbed.h"

DigitalOut myled(LED1);

int main() {
    while(1) {
        myled = 1;
        wait(0.2);
        myled = 0;
        wait(0.2);
    }
}