Skip to main content
Visitor II
October 22, 2018
Question

Is STLINK/V2 that is part of the DISCO eval board free to use?

  • October 22, 2018
  • 7 replies
  • 1099 views

Hello,

we develop a product based on an STM32F765.

Is it allowed to add a debug interface like the ones on 32F746GDISCOVERY. This would make it easier for our customers to start writing their own firmware extension.

Thank you.

    This topic has been closed for replies.

    7 replies

    Super User
    October 22, 2018

    If your customers are not likely to have their own debug/programming tools, wouldn't it make more sense to provide a bootloader so that they can can program via UART or USB?

    Visitor II
    October 22, 2018

    I would resort to a wiring of the debug pins as seen on the Nucleo boards (without the STLink part).

    That would leave customers the option to connect other debuggers (like the J-Link).

    You might ask ST if they sell you pre-programmed ST-Link MCUs. Pretty sure you will not get the firmware...

    Super User
    October 22, 2018

    Agree: providing a standard debug connector is probably a better way to go.

    http://infocenter.arm.com/help/topic/com.arm.doc.faqs/attached/13634/cortex_debug_connectors.pdf - the 10-pin, 0.05" is the favourite these days...

    I don't think ST sell the chips.

    If you really want to make your own debug adaptor, look at CMSIS-DAP - which is open source.

    Visitor II
    October 22, 2018

    Thank you for your answers.

    Of course the easiest way is to add a 10 pin or 20 pin CortexM pin header and tell the customers to buy a debugger interface of their choice.

    Components for a STLink/V2 would be ~ 8..10€ and ST publishes a BOM and firmware update files - so my assumption was the design is free to use in a customer design, but I coudn't find this info.

    Graduate II
    October 22, 2018

    >>I don't think ST sell the chips.

    @STOne-32​ Please consider selling licensed ST-LINK/V3 F7 parts

    Explorer II
    October 23, 2018

    A big selling point for us developing off the Nucleo was the drag-and-drop via USB feature so we designed it in to our end-product. Sure it was similar to CMSIS DAP but in our mind it was a feature that was part of the ST/Nucleo ecosystem so off we ran.

    Then when it came to finding the code we hit a brick wall. Eventually the wall came down and ST licensed out the code to us (binary, not source). That model has repeated itself across multiple companies over the last 4 yrs. Everything will depend on your relationship with ST on this but don't consider it an impossible issue.

    Honestly it would have been easier if ST just sold the parts pre-programmed to us. ..not sure why they have not considered that instead of trying to stop the Chinese clones on the market.

    Super User
    October 23, 2018

    Actually, the drag-and-drop is a feature from mbed.

    https://os.mbed.com/handbook/CMSIS-DAP

    DAPLink includes the drag-and-drop programming: https://os.mbed.com/docs/latest/tools/daplink.html