krishnapriya ab

Important changes to forums and questions

All forums and questions are now archived. To start a new conversation or read the latest updates go to forums.mbed.com.

9 years, 3 months ago.

Problem with my nucleol152 board.

Hello,

problem is with my nucleostm32l152 board.every time its size showing as only 12kb.I did st link software installation and its upgraded version also.After that it may show 512kb and again it will go to previous state.whats the problem with my board? Please help me to figure out the problem.

1 Answer

Nothing Special
9 years, 3 months ago.

Try this:

  • Disconect from USB
  • Insert jumper to Morpho pins ( on photo yellow jumper at the bottom). Spare jumpers are on the bottom side of Nucleo.
    /media/uploads/mega64/nucleo_boot_high.jpg
  • Connect nucleo to PC and check free size
  • If free size is correct, program chip, remove jumper and reset Nucleo.

Thank you.I connected nucleo board to X- NUCLEO-IKS01A1 sensor board.Sometimes its detecting but not constantly.What will do for this case?

posted by krishnapriya ab 14 Aug 2015

If this happens occasionally, I do not know now what might be the cause. We only know that in a short time in which STlink register as a memory stick on PC, he could not communicate with the target processor to read the size of the flash. Therefore, given the value of 0kb free space, and these 12 kB are fixed information files and directory of the disk.
I tried nucleol152 with different shields, even three at the same time and not notice problems when connecting to the USB port. I do not suppose also your X NUCLEO-IKS01A1, because there is nothing to do with lines that are used to contact STlink-Target.
The solution with a jumper, which I gave above, helps if the "mistaken" sotware blocked communication over the lines SWD on the side of the target processor. For example STM32CubeMX + Keil or IAR, for certain processors generates code that disable SWD interface by default (until it is set explicitly in the pins configuration). The result is that STlink "not see" the processor. Setting the jumper that forces high on the line boot0, starts embedded bootloader (unimportant what it does), but that does not disable these lines.

posted by Nothing Special 16 Aug 2015