Add new target: L-TEK FF1705

[gorazdko]

based on XDOT

Status: ready

[theotherjimmy]

If this target is based on the XDOT, Why does it inherit from FAMILY_STM32 and not the XDOT target?

[gorazdko]

@theotherjimmy good point. I corrected.

[theotherjimmy]

Why bother with this label if there is no code needed for this target?

[theotherjimmy]

Looks great! Thanks for minimizing it with me.

[gorazdko]

Thank you!

I have one question though. Can I add these lines inside PinNames.h of XDOT target?

#ifdef TARGET_FF1705_L151CC
    // Arduino Headers
    D0  = PA_10,
    D1  = PA_9,
    D2  = PA_11,
    D3  = PA_12,
    D10 = PB_12,
    D11 = PB_15,
    D12 = PB_14,
    D13 = PB_13,
    D14 = I2C_SDA,
    D15 = I2C_SCL,
#endif

[0xc0170]

Possibly yes, if they share both, and most of the file is the same, otherwise use separate header file

[0xc0170]

@gorazdko Can you please share any tests results that has been done on this platform?

[0xc0170]

We can squash these 3 commits into one to clean the history a bit (or can rebase), let us know. We will trigger CI then

[gorazdko]

Sure, you can squash them. Test results:
results.txt

Thanks

[0xc0170]

/morph test

[theotherjimmy]

/morph export-build

[mbed-bot]

Result: SUCCESS

Your command has finished executing! Here's what you wrote!

/morph test

Output

mbed Build Number: 1221

All builds and test passed!

[mbed-bot]

Result: FAILURE

Your command has finished executing! Here's what you wrote!

/morph export-build

Output

mbed Build Number: 132

Exporter Build failed!

[0xc0170]

@theotherjimmy This is the second failure, the same one I have seen in another PR for a new target. Please have a look

[theotherjimmy]

/morph export-build

[mbed-bot]

Result: SUCCESS

Your command has finished executing! Here's what you wrote!

/morph export-build

Output

mbed Build Number: 152

All exports and builds passed!