The special mbed_die was created because last year I was told that it will
not be possible to have a c027 specific lpc1768 platform support in mbed.
So everything was solved in the C027 lib. We have to ensure that the other
led pins of the original lpc1768 board are not used as they could damage
the c027.

The morse code was just added for fun ;) using error_led like in other
platforms is ok.

Am 29.01.2014 um 20:01 schrieb Bogdan Marinescu <notifications@github.com>:

In
libraries/mbed/targets/hal/TARGET_NXP/TARGET_LPC176X/TARGET_UBLOX_C027/C027.cpp:

> +    DigitalOut led(LED);
> +    led = 0;
> +    // Send SOS in Morse Code: // "... --- ...  "
> +    const char sos[] = "=.=.=...===.===.===...=.=.=......";
> +    const int  dot = 100; // length of the dot in milliseconds (typical: 50-100 ms)
> +    // lengths of symbols:
> +    // di         =   dot
> +    // dah        = 3 dot
> +    // char space = 3 dot
> +    // word space = 6 dot
> +    for (int i = 0; /* nothing */; i = sos[i+1] ? i+1 : 0)
> +    {
> +        led = (sos[i] == '=');
> +        wait_ms(dot);
> +    }
> +}

Is there a specific reason for which we're providing a different mbed_die
for this specific platform? If the manufacturer requested it, for example,
that's fine; otherwise it adds unnecessary fragmentation (life is more
clear when all the mbed boards behave in the same way when they "die").

--
Reply to this email directly or view it on
GitHub<https://github.com/mbedmicro/mbed/pull/153/files#r9279068>
.

-- 
You received this message because you are subscribed to the Google Groups
"mbed-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to mbed-devel+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.