This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

STM32L programminf problem

Hi!

I try to migrate my device from STM32F103RB to STM32L152RB and have faced the following problem. After succesfull compiling Keil uVision (4.13a) returns error then I try to download code in flash memory:

Build target 'STM32L152 Flash'
assembling startup_stm32l1xx_md.s...
compiling system_stm32l1xx.c...
compiling Blinky.c...
compiling IRQ.c...
compiling GLCD_SPI_STM32L.c...
compiling ARM_Ani_16bpp.c...
linking...
Program Size: Code=4240 RO-data=108292 RW-data=5428 ZI-data=516
".\Flash\Blinky.axf" - 0 Error(s), 0 Warning(s).
Load "C:\\Keil\\ARM\\Boards\\ST\\STM32L152-EVAL\\LCD_Blinky\\Flash\\Blinky.AXF"
Set JLink Project File to "C:\Keil\ARM\Boards\ST\STM32L152-EVAL\LCD_Blinky\JLinkSettings.ini"

JLink info:
------------
DLL: V4.20c, compiled Sep 24 2010 19:46:42
Firmware: J-Link ARM-Pro V1.x compiled Sep 24 2010 17:25:38
Hardware: V1.10
S/N : 171100029
Feature(s) : RDI, FlashBP, FlashDL, JFlash, GDB

* JLink Info: Found SWD-DP with ID 0x2BA01477
* JLink Info:   FPUnit: 15 code (BP) slots and 15 literal slots
**JLink Warning: CPU core not found.
No debug information for index 0x0100 available on this CPU.


What I do wrong?

Regards,
Ilya.

  • And I don't understand why this window (www.flickr.com/.../53850447@N05/5160652951/ "SEGGER J-Link V4.20c - Emulator selection") displays three times (I have to press "OK" three times!) if I try to "update".

    Regards,
    Ilya

  • The first problem was solved, but instead there was another problem:

    Build target 'STM32L152 Flash'
    assembling startup_stm32l1xx_md.s...
    compiling system_stm32l1xx.c...
    compiling Blinky.c...
    compiling IRQ.c...
    compiling GLCD_SPI_STM32L.c...
    compiling ARM_Ani_16bpp.c...
    linking...
    Program Size: Code=4240 RO-data=108292 RW-data=5428 ZI-data=516
    ".\Flash\Blinky.axf" - 0 Error(s), 0 Warning(s).
    Load "C:\\Keil\\ARM\\Boards\\ST\\STM32L152-EVAL\\LCD_Blinky\\Flash\\Blinky.AXF"
    Set JLink Project File to "C:\Keil\ARM\Boards\ST\STM32L152-EVAL\LCD_Blinky\JLinkSettings.ini"
    
    JLink info:
    ------------
    DLL: V4.20c, compiled Sep 24 2010 19:46:42
    Firmware: J-Link ARM-Pro V1.x compiled Sep 24 2010 17:25:38
    Hardware: V1.10
    S/N : 171100029
    Feature(s) : RDI, FlashBP, FlashDL, JFlash, GDB
    
    * JLink Info: Found SWD-DP with ID 0x2BA01477
    * JLink Info: TPIU fitted.
    * JLink Info: ETM fitted.
    * JLink Info:   FPUnit: 6 code (BP) slots and 2 literal slots
    ROMTableAddr = 0xE00FF003
    
    Target info:
    ------------
    Device: STM32L152RB
    VTarget = 3.429V
    State of Pins:
    TCK: 0, TDI: 0, TDO: 1, TMS: 0, TRES: 1, TRST: 1
    * JLink Info: Found SWD-DP with ID 0x2BA01477
    * JLink Info: TPIU fitted.
    * JLink Info: ETM fitted.
    * JLink Info:   FPUnit: 6 code (BP) slots and 2 literal slots
    Hardware-Breakpoints: 6
    Software-Breakpoints: 2048
    Watchpoints:          4
    JTAG speed: 500 kHz
    
    Erase Done.
    Programming Done.
    Contents missmatch at: 08000000H  (Flash=00H  Required=38H) !
    ... ... ...
    ... ... ...
    ... ... ...
    Contents missmatch at: 0800008EH  (Flash=D9H  Required=00H) !
    Too many errors to display !
    


    What's wrong?

  • Would you care to share how it was solved?

  • The first problem has passed into the second after decreasing max clock to 2 MHz (or less). But how can I solve the second problem??

  • Another interest fact that the same STM32L fully workable with STlink! I can program and debug. Why I can not do it with J-Link Pro?

  • Must be something related to the J-Link, then!

    eg:

    The J-Link itself;

    Drivers;

    Configuration;

    A combination of the above.

    As the STM32L is a new part, are you sure that everything is fully up-to-date for your J-Link to support it?
    (there are various updates on the ST site)

  • Yes, I'm sure!
    I have 2 J-link (Pro and Ultra). J-Link PRO firmware was updated to the last version. Trying to update J-link Ultra firmware (from Keil 4.13a) leads to Keil hangs off. And firmware download isn't succesfully complete. With Keil 4.12 both debuggers works correctly (but STM32L not supported in 4.12 version). J-Link PRO work correctly in v.4.13a with STM32F... but not with STM32L. And another problem that this boring window pops three times at every operation...

  • Now I try to use ULINK-ME... and the same problem - programming failed!
    So the only workable debugger by SWD for STM32L is STlink ???

  • Hi,

    can you open a support ticket to Keil?

    Changes made to the JLink driver:
    - updated to latest Segger drivers (stable version)
    - changed behaviour of scanning for JLinks (USB select box does not appear anymore)

    I cannot attach any files here, but if you open a ticket you can receive the new files asap.

    .
    BR,
    /th.

  • I have already addressed same problem to support (from Keil menu "help -> contact support"). But there aren't any response from support during one week...