Friday, November 24th 2017, 9:06pm UTC+1

You are not logged in.

  • Login
  • Register

jjacobson

Beginner

Date of registration: Oct 5th 2017

Posts: 2

1

Friday, October 13th 2017, 6:19pm

[ABANDONED] STM32L496VGT incorrect RAM size in Segger tools (Flasher and Ozone)

I'm using an STM32L496VGT in a design and ST is telling me the RAM size is 320k, but the Segger tools indicate this is only 96k. Can someone help confirm where the 96k number is coming from? Thanks.

SEGGER - Niklas

Super Moderator

Date of registration: Oct 6th 2014

Posts: 1,691

2

Monday, October 16th 2017, 9:17am

Hi,


the SEGGER tools show the size of the work RAM J-Link is aware of and will use.
It does not necessary indicate the actual amount of RAM available on a device.

Best regards,
Niklas
Would you like to be added to the J-Link software update notification list, so you get informed automatically when a new version becomes available?
Just write me a PM or in case you want to subscribe to it yourself, please use this link: Link
Notification for J-Link, J-Link Debugger, SystemView & J-Scope: Link
Notification for Embedded Studio: Link

jjacobson

Beginner

Date of registration: Oct 5th 2017

Posts: 2

3

Tuesday, October 17th 2017, 1:20am

Hi Niklas,

Thanks for the reply. with most of the other controllers in the family the J-Link supports the 320k size. Do you know if Segger will be updating that in the next software release? And if so, do you know what that release schedule looks like?

Thanks,

Jon

SEGGER - Nino

Super Moderator

Date of registration: Jan 2nd 2017

Posts: 352

4

Thursday, October 19th 2017, 10:39am

Hello Jon,

Niklas is currently not available so i will try to answer your question.

Quoted

It does not necessary indicate the actual amount of RAM available on a device.

What Niklas wanted to say with this is that any J-Link will support any RAM that exists.
The number that is shown in our tools is just the "guaranteed" RAM for our tools that will be initialized and usable.
Some chips need extra initialization for other RAM segments, that is why we stick to the "always available" RAM.

But any other memory type that is correctly used and initialized by the user will be read- and writeable by J-Link.
So if there are 320k RAM and it is initialized, you can use it.

Best regards,
Nino