Wednesday, May 23rd 2018, 10:28pm UTC+2

You are not logged in.

  • Login
  • Register

Search results

Search results 1-20 of 78.

Tuesday, March 27th 2018, 3:24pm

Author: Kenny

[SOLVED] Trace of function loaded to RAM.

Re-reading my own post, there is the original question: Why didn't execution halt on the second hardware breakpoint? Especially if the trace addresses are reliable. I did eventually resolve this issue. Interrupt code was running in the same block during a program or erase of a sector in that same block. That's why a routine was copied to RAM. This is known problem with these processors but it is not well described in their application note. Maybe there is a hardware bug of some kind or a limitat...

Tuesday, March 27th 2018, 3:09pm

Author: Kenny

[SOLVED] Trace of function loaded to RAM.

Yes. Knowing that the addresses are dependable is very helpful. Thank you.

Monday, March 26th 2018, 7:02pm

Author: Kenny

[SOLVED] Trace of function loaded to RAM.

I believe these conditions were satisfied during my last debugging session. I understand that in my original setup, where ReadIntoTraceCache is called in AfterTargetDownload, might have been a problem. Do you think you can describe how the debugger interacts with the ETM/ETB a little more deeply? When ReadIntoTraceCache is called does that build a map of addresses and the instructions in memory (at that time of course)? Then the ETM is configured to deliver only addresses to the ETB? The debugge...

Thursday, March 22nd 2018, 8:22pm

Author: Kenny

[SOLVED] Trace of function loaded to RAM.

These are not garbage instructions. They are the correct block copied from flash. I also tried an experiment where I only called ReadIntoTraceCache with the exact amount required for the function and got Unknown Addresses.

Monday, March 19th 2018, 6:38pm

Author: Kenny

[SOLVED] Trace of function loaded to RAM.

My target processor is a Kinetis K64 which has an ETB. I am using trace with Ozone over SWD. At first I was getting Unknown Address in the trace listing and corrected this by adding Exec.Command("ReadIntoTraceCache 0x1FFF0000 0x40000") to AfterTargetDownload(). A block of flash beginning with the function of interest is copied to RAM and that function is called using the appropriate pointer-to-function. The copied block is larger than the function of interest so additional, unused, instructions ...

Thursday, January 11th 2018, 4:00am

Author: Kenny

[SOLVED] OS_EnterInterrupt/OS_EnterNestableInterrupt on Cortex-M

I have two timer interrupts which both use OS_Enter/OS_LeaveInterrupt. One has a higher priority than the other. Both are at lower priorities (higher values) than the fast interrupt. My understanding is that these routines disable interrupts that are not so-called fast interrupt. Using a scope I set two GPIOs high when entering these routines and low when leaving. I can clearly see the lower interrupt preempted by that with the higher priority. From the Cortex-M EMBOS manual: Quoted OS_EnterInte...

Thursday, January 5th 2017, 5:09am

Author: Kenny

[Resolved] J-Trace with STM32F746

Silly mistake on my end. I had the 19-pin adapter connected to the Target side instead of direct cable to Target + Trace. ...... I'm not seeing any trace data. Traceport with 4-bit is selected. When I step the Trace LED blinks orange and the debugger stepping is definitely slower. If I run the Trace LED is always orange. This is a custom board. J-Trace for Cortex-M V3.2 SES 3.10i OS X 10.11.6 (El Capitan)

Monday, December 12th 2016, 6:34pm

Author: Kenny

Flashing (1 Hz) Red LED

It's 500/500 ms. It does this when disconnected from the target altogether. Had no functional issues all weekend while debugging. Actually the red/green is appropriate for the holidays.

Saturday, December 10th 2016, 7:59pm

Author: Kenny

Flashing (1 Hz) Red LED

Hi, I have a JLink Plus V9.3 attached to a new board containing an STM32F746 and the red LED is flashing at 1 Hz. The manual suggests that this is a fatal error. So far things seem to be working correctly. The board brings out trace to the 19-pin Cortex connector. Thanks, Kenny

Sunday, November 13th 2016, 7:12am

Author: Kenny

STM32F746 Nucleo SES Git Repository

There is no application but DHCP is working and acquires a lease. PHY address was set to 1 by default in Cube rather than 0.

Sunday, November 13th 2016, 5:26am

Author: Kenny

STM32F746 Nucleo SES Git Repository

I used the ST Cube software to export source as an Atollic TrueStudio project and imported it into SES. My goal is simply to get the LWIP stack up and running with FreeRTOS on the STM32F746 Nucleo board. This first commit will build and prints 'Hello' once a second to the output window using RTT. My next step is to see if I can one of the basic LWIP demos to run. Maybe it will right away but if it doesn't then perhaps others may be interested to help me get this going. If nothing else you may re...

Saturday, November 12th 2016, 7:48pm

Author: Kenny

Improvements to Dynamic Folders (Feature Requests)

It would be useful if one could recursively convert a dynamic folder to a regular one. Also would it be possible to exclude an item in a dynamic folder from a build? I'm exporting code from ST Cube, creating an SES project, then importing that code using dynamic folders (because there are many and they are deep). I would like to exclude the vectors and reset handler and use those provided by SES. As it stands the easiest thing to do is remove those unwanted files (or at least move them to a fold...

Wednesday, October 26th 2016, 8:27pm

Author: Kenny

SES 3.10e trouble identifying hard fault

Commenting and uncommenting code is likely to confuse the issue when you have something like a hard fault. I'm actually battling one myself right now on an STM32F415. The system control block has some registers that you can inspect that can be helpful. Check your stacks for overflow if you are using an RTOS (the plugins for EMBOS and FreeRTOS will display this information). You can find hard fault handler code out there that will pull useful information off the stack. The real tool to use for th...

Wednesday, October 26th 2016, 8:15pm

Author: Kenny

Trace with SWO

This somehow fixed itself. Can now connect but I'm not getting any data. I do have SWO run to pin 6 of the so-called 9-pin connector. I simply enabled SWO as a trace option and tried some things with the trace window open in the debugger.

Wednesday, October 26th 2016, 5:44pm

Author: Kenny

Trace with SWO

When attempting to use trace with SWO I get a dialog "connect failed". The last line in the output window is: Executing script EnableTrace("SWO"). My target is an STM32F415. SES 3.10e. Best regards, Kenny

Wednesday, October 26th 2016, 2:56am

Author: Kenny

J-Link, 5V Supply

Hi Torsten, I do not think that the JLink 5V is enabled by default. Use JLink Commander to enable it permanently: power <state> [perm] is the syntax. Kenny

Monday, October 10th 2016, 9:56pm

Author: Kenny

__ARMVFP__

I believe this is another artifact of the EWARM import. I have given up on this approach and exported Atollic projects from Cube which has been successful.

Monday, October 10th 2016, 9:52pm

Author: Kenny

tmp* files on OS X

I've defined a single directory for my compiler output (*.d, *.o, *.elf, *.map etc). Over time I see a large number of files whose names begin with 'tmp'. Is this a bug? Can it be disabled? Silverback: ls tmp* tmpT2z7aY tmpgRuLoX tmptffH8U tmpyFE8nZ They seem to contain assembler output: .syntax unified .cpu cortex-m7 .eabi_attribute 28, 1 .fpu fpv5-d16 .eabi_attribute 20, 1 .eabi_attribute 21, 1 .eabi_attribute 23, 3 .eabi_attribute 24, 1 .eabi_attribute 25, 1 .eabi_attribute 26, 1 .eabi_attrib...

Sunday, October 9th 2016, 12:47am

Author: Kenny

__ARMVFP__

My imported ST Cube project is complaining: Quoted #ifndef __ARMVFP__ #error This port can only be used when the project options are configured to enable hardware floating point support. #endif I've selected hard floating point and the correct architecture in `Code Generation` (see attached). I can hack this and try to define this macro but what is the proper way to get this work. I have another (non-Cube) based project that does not use the ST HAL for this same processor with FreeRTOS integrate...