[SOLVED] STM32l0 support

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • Hi,

    Sorry for the late reply, busy days...
    We are currently working on STM32L0 support and hope to have this ready by the end of next week (maybe earlier).
    It is planned to be part of V4.87a (beta).


    - Alex
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.

  • Hi,

    Sorry for the delay. Busy days...
    V4.88 has been released which comes with support for the L0 series devices.
    Download-Link: segger.com/jlink-software.html


    - Alex
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.


  • - DLL/J-Flash: Added flash programming support for ST STM32L0x1, STM32L0x2 and STM32L0x3 devices. (Cortex-M0)




    Hi,

    unfortunately, the support for the STM32L052K8 is not working for us. The J-Link adapter cannot connect to the core.
    If we setup "Cortex-M0+" as device, then it is connecting without any problem. Also a ST-Link V2 Debug-Interface is working without any problems.

    It also seems that the sizes of RAM/ROM for the new devices are not correct sometimes in the presented selection table.

  • Hi,

    It would be *extremely* helpful if you could post some error messages etc. you are getting...
    What software did you use to connect to the device?
    Is J-Link Commander able to connect to the device / identify it?
    Can you post the output of J-Link Commander?
    What board are you using?

    What I can say: It is working absolutely fine here on an eval board we used as reference. I will post the exact board name tomorrow.


    - Alex
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.

  • Sure, sorry.

    I have tried J-Link Commander and J-Link GDB server.

    The RAM/ROM sizes do not match and the core type does not match. The STM32L052K8 features a Cortex-M0+ with MPU.
    The STM32L052K8 has 64KB of flash, 2KB of EEPROM and 8KB RAM.
    See here: st.com/st-web-ui/static/active…/datasheet/DM00108217.pdf

    Output of J-Link commander (just started by clicking the desktop icon,
    then I have entered "device stm32l052k8" after it automatically detected
    the general Cortex-M0 core):

    Source Code

    1. SEGGER J-Link Commander V4.88b ('?' for help)
    2. Compiled Jul 21 2014 16:17:04
    3. DLL version V4.88b, compiled Jul 21 2014 16:16:56
    4. Firmware: J-Link ARM V8 compiled Jul 17 2014 12:31:18
    5. Hardware: V8.00
    6. S/N: 5800XXXX
    7. VTarget = 3.041V
    8. Info: Found SWD-DP with ID 0x0BC11477
    9. Info: Found Cortex-M0 r0p1, Little endian.
    10. Info: FPUnit: 4 code (BP) slots and 0 literal slots
    11. Found 1 JTAG device, Total IRLen = 4:
    12. Cortex-M0 identified.
    13. Target interface speed: 100 kHz
    14. J-Link>device stm32l052k8
    15. Info: Device "STM32L052K8" selected (66 KB flash, 4 KB RAM).
    16. Reconnecting to target...
    17. Info: Found SWD-DP with ID 0x0BC11477
    18. Info: STM32 (connect): Can not attach to CPU. Trying connect under reset.
    19. Info: Found SWD-DP with ID 0x0BC11477
    20. Info: Found Cortex-M0 r0p1, Little endian.
    22. WARNING: Identified core does not match configuration. (Found: Cortex-M0, Config
    23. ured: Cortex-M3)
    24. Info: FPUnit: 4 code (BP) slots and 0 literal slots
    25. J-Link>
    Display All

  • Output of J-Link GDB server(command line: -select USB -device STM32L052K8 -if SWD -speed 100):

    Source Code

    1. SEGGER J-Link GDB Server V4.88b LogFile
    2. Logging started @ 2014-07-22 11:13
    3. 03-00000000-00-00000000-001F: SEGGER J-Link GDB Server V4.88b
    4. 03-00000000-00-00000000-000C: GUI Version
    5. 03-00000000-00-00000000-0037: JLinkARM.dll V4.88b (DLL compiled Jul 21 2014 16:16:56)
    6. 03-00000000-00-00000002-0023: -----GDB Server start settings-----
    7. 03-00000000-00-00000002-0023: GDBInit file: none
    8. 03-00000000-00-00000003-0023: GDB Server Listening port: 2331
    9. 03-00000000-00-00000003-0023: SWO raw output listening port: 2332
    10. 03-00000000-00-00000003-0023: Terminal I/O port: 2333
    11. 03-00000000-00-00000003-002D: Accept remote connection: localhost only
    12. 03-00000000-00-00000003-0021: Generate logfile: on
    13. 03-00000000-00-00000003-0022: Verify download: off
    14. 03-00000000-00-00000003-0021: Init regs on start: on
    15. 03-00000000-00-00000003-0022: Silent mode: off
    16. 03-00000000-00-00000003-0022: Single run mode: off
    17. 03-00000000-00-00000003-0025: Target connection timeout: 5 sec.
    18. 03-00000000-00-00000003-0023: ------J-Link related settings------
    19. 03-00000000-00-00000003-0022: J-Link Host interface: USB
    20. 03-00000000-00-00000003-0023: J-Link script: none
    21. 03-00000000-00-00000003-0023: J-Link settings file: none
    22. 03-00000000-00-00000003-0023: ------Target related settings------
    23. 03-00000000-00-00000003-002A: Target device: STM32L052K8
    24. 03-00000000-00-00000003-0022: Target interface: SWD
    25. 03-00000000-00-00000003-0025: Target interface speed: 100kHz
    26. 03-00000000-00-00000003-0025: Target endian: little
    27. 03-00000000-00-00000004-0017: Connecting to J-Link...
    28. 02-00000000-00-00000022-0035: Firmware: J-Link ARM V8 compiled Jul 17 2014 12:31:18
    29. 02-00000000-00-00000022-000F: Hardware: V8.00
    30. 02-00000000-00-00000034-0032: S/N: 5800XXXX returns O.K. (0030ms, 0030ms total)
    31. 03-00000000-00-00000034-0014: J-Link is connected.
    32. 02-00000000-00-00000035-0061: T0D74 000:035 JLINK_ExecCommand("device = STM32L052K8", ...) returns 0x00 (0001ms, 0031ms total)
    33. 02-00000000-00-00000035-0068: T0D74 000:036 JLINK_ExecCommand("SetFlashRewriteBehavior = 1", ...) returns 0x00 (0000ms, 0031ms total)
    34. 02-00000000-00-00000036-0041: T0D74 000:037 JLINK_GetFirmwareString(...) (0000ms, 0031ms total)
    35. 03-00000000-00-00000036-0035: Firmware: J-Link ARM V8 compiled Jul 17 2014 12:31:18
    36. 02-00000000-00-00000036-0050: T0D74 000:037 JLINK_GetHardwareVersion() returns 0x13880 (0000ms, 0031ms total)
    37. 03-00000000-00-00000036-000F: Hardware: V8.00
    38. 03-00000000-00-00000036-000D: S/N: 58007407
    39. 02-00000000-00-00000038-0049: T0D74 000:037 JLINK_GetHWStatus(...) returns 0x00 (0002ms, 0033ms total)
    40. 02-00000000-00-00000038-003C: T0D74 000:039 JLINK_EnableSoftBPs(ON) (0000ms, 0033ms total)
    41. 03-00000000-00-00000038-001A: Checking target voltage...
    42. 03-00000000-00-00000038-0016: Target voltage: 3.04 V
    43. 03-00000000-00-00000038-001D: Listening on TCP/IP port 2331
    44. 03-00000000-00-00000038-0017: Connecting to target...
    45. 02-00000000-00-00000038-0035: T0D74 000:039 JLINK_ClrError() (0000ms, 0033ms total)
    46. 02-00000000-00-00000040-0049: T0D74 000:039 JLINK_GetHWStatus(...) returns 0x00 (0002ms, 0035ms total)
    47. 02-00000000-00-00000046-0055: T0D74 000:041 JLINK_TIF_Select(JLINKARM_TIF_SWD) returns 0x00 (0006ms, 0041ms total)
    48. 02-00000000-00-00000048-0038: T0D74 000:047 JLINK_SetSpeed(100) (0002ms, 0043ms total)
    49. 02-00000000-00-00000048-0043: T0D74 000:049 JLINK_GetSpeed() returns 0x64 (0000ms, 0043ms total)
    50. 02-00000000-00-00000048-0077: T0D74 000:049 JLINK_SetResetType(JLINKARM_RESET_TYPE_NORMAL) returns JLINKARM_RESET_TYPE_NORMAL (0000ms, 0043ms total)
    51. 02-00000000-00-00000048-003B: T0D74 000:049 JLINK_SetResetDelay(0) (0000ms, 0043ms total)
    52. 02-00000000-00-00000048-0055: T0D74 000:049 JLINK_SetEndian(ARM_ENDIAN_LITTLE) returns 0x00 (0000ms, 0043ms total)
    53. 02-00000000-00-00000202-01EC: T0D74 000:049 JLINK_Connect() >0x108 TIF> >0x0D TIF> >0x28 TIF> >0x0D TIF> >0x28 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x28 TIF> >0x0D TIF> >0x28 TIF> >0x0D TIF> >0x28 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF>STM32 (connect): Can not attach to CPU. Trying connect under reset. >0x108 TIF> >0x0D TIF> >0x28 TIF> >0x0D TIF> >0x28 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x28 TIF> >0x0D TIF> >0x28 TIF> >0x0D TIF> >0x28 TIF> >0x0D TIF> >0x21 TIF> >0x0D TIF> >0x21 TIF> returns 0xFFFFFFFF
    54. 02-00000000-00-00000202-0017: (0154ms, 0197ms total)
    55. 03-00000000-00-00000202-0023: ERROR: Could not connect to target.
    56. 03-00000000-00-00000202-0035: Target connection failed. GDBServer will be closed...
    57. 03-00000000-00-00002213-0037: Restoring target state and closing J-Link connection...
    58. 02-00000000-00-00002213-0041: T0D74 002:214 JLINK_IsOpen() returns 0x01 (0000ms, 0197ms total)
    59. 02-00000000-00-00002213-0056: T0D74 002:214 JLINK_ExecCommand("ClrAllBPs", ...) returns 0x00 (0000ms, 0197ms total)
    60. 03-00000000-00-00002402-0010: Shutting down...
    Display All
    Images

    • screenshot.1.png

      20.78 kB, 720×470, viewed 822 times

    The post was edited 2 times, last by tesler ().

  • Hi,

    Thanks for posting.
    Looks like a typo (and then copy & paste mistake) in the J-Link software...
    We will investigate and correct this. The L0 series are definitely Cortex-M0+ and not M3...


    - Alex
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.

  • Hi,

    We determined the problem here and already fixed it.
    The fix will be included in the next official version of the J-Link software.


    Best regards
    Erik
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.

  • Hi Christian,

    Tomorrow. It will be V4.90.


    - Alex
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.

  • Hi all,

    Release has been rescheduled for Monday morning.
    We are currently working on adding a new component to the software package, so this created some delay.


    - Alex
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.

  • Hi all,

    Has been fixed in V4.90:
    segger.com/jlink-software.html


    - Alex
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.

  • Hi Christian,

    Thanks for the confirmation.
    We will close this thread then.


    - Alex
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.