Posts by SEGGER - Matthias

Hello,

I cannot reproduce this with J-Scope V7.94c.

Could you create a ticket through our support ticket system and include the ELF file with which this is reproducible?
https://support.segger.com/

Hello all,

thanks for the report.

I was able to reproduce this with one of my test ELF files while others work fine. We will investigate this and will try to have a fix included with the next version.

Best regards,
Matthias

Hello,

thanks for the report.

This issue has been resolved with V7.92q which was released yesterday.

Best regards,
Matthias

Hello,

thanks for the report. Could you provide the .ELF file for reproduction purposes?

Best regards,
Matthias Konegen

Hello,

Alex asked me to have a look into this.

Your XML file is good - at least for the current release version of the J-Link software.

At the time of V7.64 the <LoaderInfo> tag was not yet supported, so V7.64 does not know how to handle it. The information which is currently provided by the <LoaderInfo> tag was handled entirely by the parent <FlashBankInfo> tag. J-Link is still backward-compatible to the old format, but it is no longer recommended to use it. Instead we recommend using the current version of the J-Link software.

If your setup absolutely requires V7.64 you may adapt your XML entries to the following format:

<DataBase>
<Device>
<ChipInfo Vendor="<Vendor>" Name="<Name>" WorkRAMAddr="<WorkRAMAddr>" WorkRAMSize="<WorkRAMSize>" Core="<Core>" />
<FlashBankInfo Name="<Name>" BaseAddr="<BaseAddr>" AlwaysPresent="<AlwaysPresent>" MaxSize="<MaxSize>" Loader="<Loader>" LoaderType="FLASH_ALGO_TYPE_OPEN" />
</Device>
</DataBase>

Best regards,
Matthias

Hello,

Fabian will be out of office for the next weeks, so please allow me to take over.

Our wiki contains a description that explains the FlashDevice struct ant its SectorInfo array.
https://wiki.segger.com/SEGGER_Flash_L…shDevice_struct

E.g.:

// FlashDevice.TotalSize:// 0x40000//// FlashDevice.SectorInfo[]:// {// SectSize StartAddr// { 0x00004000, 0x00000000 }, // 4 * 16 KB = 64 KB// { 0x00010000, 0x00010000 }, // 1 * 64 KB = 64 KB// { 0x00020000, 0x00020000 }, // 1 * 128 KB = 128 KB// { 0xFFFFFFFF, 0xFFFFFFFF } // Indicates the end of the flash sector layout. Must be present.// }

This SectorInfo array has sectors of size 0x4000 that go from 0x00000000 (relative to the base address of the flash) to 0x00010000. This means that there are four 0x4000 sectors between 0x00000000 and 0x00010000.
Above 0x00010000 the sector size is 0x10000 and this block of uniform sectors goes from 0x00010000 to 0x00020000. This means that there is one 0x10000 sector between 0x00010000 and 0x00020000.
Above 0x00020000 the sector size is 0x20000 and this block of uniform sectors goes from 0x00020000 to the end of the flash (in this case 0x00040000). This means that there is one 0x20000 sector between 0x00020000 and 0x00040000.

I hope this clears it up.

Best regards,
Matthias

Hello,

a fix for this issue is ready and will be included in the next version of the J-Link software scheduled for some time next week.

Best regards,
Matthias

Hello,

thanks for bringing this to our attention. We will have a look at this with the next iteration.

Best regards,
Matthias

Hello,

please see our wiki regarding the use of J-Scope with RTT.
https://wiki.segger.com/UM08028_J-Scop…it_with_J-Scope

Your usage simply logs a string to an RTT buffer. With J-Scope you need to create a RTT buffer and write the values of the variables into it.

Best regards,
Matthias

Hello,

we are not aware of such an issue with V7.80d.

Is it possible for you to provide a simple reproducer setup (XML, ELF and custom flashloader project)?

Best regards,
Matthias

Thanks for the confirmation.

Will will consider this case closed.

Hello,

the issue you are seeing seems to be the previously mentioned one about the crash during sampling. V7.66c was released on Wednesday and includes a fix for that. Could you check out the newest version?

Best regards,
Matthias

Hello,

did you try creating a new project for this? (File -> New Project ...)

At first look it seems to me that this is an existing project that was saved with no symbols selected. To select symbols, you can press the "+" button in the bottom table.

Please note that there is a bug in the current release (V7.66b) of J-Scope which may cause issues during sampling. A fix for this bug is ready and will be included in V7.66c which is scheduled for later today.

Best regards,
Matthias

Hello,

I have found a possible cause for the behavior which you are seeing. This was introduced with V7.60d, so it would fit that you are not seeing it with V7.60b.
A fix for this issue is ready and will be included with V7.66c of the J-Link software package which should be released within the next week.

Once released, could you give this a try and tell me, if the issue is resolved?

Best regards,
Matthias

Hello,

thanks for providing this information. We are not aware of such an issue.

I will have a look at this and get back to you with the results.

Best regards,
Matthias

Hello,

a fix for this issue is ready and will be included in the next version (7.64f) of the J-Link software package scheduled for some time next week.

Thank you for bringing this to our attention.

Best regards,
Matthias

Hello,

there was an issue with the options dialog introduced with J-Scope V7.64c. It has been resolved with V7.64d. Would you download the new version and check if it resolves the issue you are seeing?

Best regards,
Matthias

Hello,

thank you for your inquiry. It is good to see that the issue could already mostly be solved.

You can indeed set the Y-Zoom/Y-Resolution independently for each variable.

There is currently no option to adapt the line draw thickness. Thank you for the suggestion, we will consider adding it with a future update.

Best regards,
Matthias

Hello,

we are not aware of any issue like this. Could you please create a ticket about this issue with our support ticket system?
https://support.segger.com/

It makes keeping track of different issues a lot easier.

Thanks
Matthias

Hello,

I have sent you a private message for sharing the .elf file.

Best regards,
Matthias