Hello Segger Team,
When trying to copy a selected Folder in the Project Explorer via the shortcut CTRL-C/CTRL-V it is always failing until using the Copy-Function from the context-Menu. After using this, the CTRL-C-Copy is also working.
You can reproduce it with the default Project when copying the Setup Folder into the Source folder, or vice versa.
Regards
Hello hiqrf3,
are you using multiple projects in a single solution?
In this scenario the indexer seems not to work in embedded Studio, or at least not working properly when regularly switching between these projects.
Regards
Hello Nino,
I’ve only enabled the „Use Tabs” Setting for C and C++ like this:
Tools --> Options --> Languages
And I enabled the visibility of white spaces to make the behavior better observable
Edit --> Others --> Visible White Spaces
Use the default project and ‘tabbify’ it like this:
Press Enter after the printf-statement. Embedded Studio is automatically intending to the level of the printf statement. If you type a new statement here it is intended with spaces instead of tabs.
Should be easy to reproduce.
Best Regards
Hello Segger Team,
when Tabs are configured, spaces are still used for automatic indentation.
For example this code from the default project:
When pressing enter at the end of the line with the printf-statement to enter an additional printf statement, spaces are used to intend.
In addition, the default values of the options are bit uncommon. Why distinguish between “Tab Size” and “Indent Size”? When “Tab Size” is not identical to “Indent Size” the Indentation is filled with spaces. Why differentiate here?
In addition, the default size of eight columns for the “Tab Size” is also very uncommon. I think four is used most and should therefore be default.
Regards
Hello v01d,
I do not think I understand you. Because, I _can_ connect & debug multi-core (multi ARM A core) to be specifically, on a SoC I used. Not only that, but with single JTAG I can connect to 2 A cores (SMP config) and one M core at the same time (for AMP thus).
within a single instance of … whatever software you are using?
It is possible to connect to multiple cores of a single controller with a single J-Link adapter. But you have to use multiple instances of the Application; one for each core.
Accessing multiple cores within a single instance of the Application is not possible as far as I have understood it. That was what you have asking for, correct?
Best Regards
Hello v01d,
we had also the same problem, so I think I can answer your question.
Quick answer: No it is not possible.
The problem is not Embedded Studio, but the J-Link Adapter.
We had the same problem with a different Development Environment which supports what you are requesting for. However, we couldn’t use it as the JTAG-Adapter has to support multi-core debugging. J-Link doesn’t ☹. Therefore, we had to switch to a different vendor. Hope Segger is adding this feature as we would like to use the J-Links.
A different Solution would be to debug each core with an own instance of embedded Studio. This should work but wasn’t a solution for us.
Hope this helps.
Best Regards
Hello Matthew,
There is also a theme option under “Environment” -> “Theme”. This one makes the whole application dark, not only the Code-Editor. But seems like there is a problem with this option on MacOS. Compare this thread:
https://forum.segger.com/index.php/Thre…23230#post23230
Regards
Hello Matthew,
1)
- Select your project in the Project Explorer
- select project -> Properties in the menu. Or select “Edit properties” in the Context Menu
- search for “Optimization level”
- select the one you like
Hint: you can use separate Optimization levels for separate folders and Files. If you want to configure the whole project ensure you have selected the whole project in the Project explorer
Hint2: If you want to have the optimization enabled only in release Build enshure to select "Relese" in the top-left combobx of the Properties Window
2)
- Select Tools -> Options in the Menu
- Go to “Environment” -> “Theme” (second last),
- Select “Dark”
Regards
The “Close All” entry of Context-Menu which comes up when you do an ”long-left-click” on the big X on the upper right corner (where you are closing opened files) of theSource-Code-Dock seems to do what you are searching for.
Best Regards
I think Segger will only support their own JTAG-Interface. But the older sibling of SES supports CMSIS-DAP.
Regards
Hello Nino,
Tanks for the feedback.
Unfortunately, there are still problems. When switching the ‘Wide Character Size’ Option to 16-bit. CLANG is creating an error while GCC is working.
Do you have also a solution for this?
Best Regards
Hello Segger Team,
I’m getting some errors when using STL with the CLANG compiler, gcc is working fine. I’ve attached an example to demonstrate this errors.
You can remove the first error by setting the compiler option -fno-signed-char but I think the project behavior should be same without setting extra options for each compiler.
Could you take a look at this compiler errors?
Best Regards
Sorry for the late response I was out of the office.
Sadly, I don’t have any code or binary’s left from this scenario.
Right now a colleague had a similar problem with a different controller (KV11). He had flashed a binary which was compiled for a different derivate (K02 I think). Ending up with a controller which had the same behavior as mine bevor.
When I had brickt my board I was also switching between different Kinetis-controllers. Maybe I had done the same mistake.
I had done this mistake also in the past, but I had never bricked a controller with it. I could always erase and flash it again. Maybe that’s why I’m not as careful as I should with this.
I will try to get some old boards next week and try to brick them.
Thanks and regards
Markus
Hello Niklas,
the FRDM-K22F board has a red LED which signals the state of the reset line. And it is flickering while the jlink is trying to connect. In addition you can hold the reset line manually high with pushing the SW1 Bumper. I have done so (with the OpenSDA Interface and in a second try with an external JLink) with the same negative result.
-->The Reset line seems to work, but it doesn’t lead to any success.
You are right; the controller seems to be in a state where the J-Link can’t access. I think it is related with the clocking system. I had made some changes there and while testing them, the controller got stuck. I haven’t this particular code anymore, and I don’t want to force it and brick an additional board. But I could send you one of my boards if it would help.
Regards
Markus
Hey Niklas,
now I’m getting the same error than in ozone.
Regards
Markus
Hello Niklas,
Are you sure with the device-string? I’m getting an error with it (see the picture attached)
Regards
Markus
Hello Niklas,
My second Board is also not working anymore. Same behavior, it stopped working after a debug session. The software to debug crashed at some point, and ended up with a board which does to respond to the debugger anymore.
I had a similar behavior some time ago with TI Stellaris controller. TI had provided a tool to get the controller working again; with normal JTAG-Adapters you couldn’t gat any access.
Regards
Markus
Hello Niklas,
I’m using Ozone in Version 2.42. I’m not sure which JLINK driver Version is used, as I have installed several versions in parallel. I have uninstalled all Versions except the newest available (6.16f). But I have still the same error.
What I have to mention, the debug connection has worked once, and after this, I’m not able to start the debugger again. Maybe I have brickted my Board by debugging it.
I’m not familiar with the J-Link Commmander, but it looks like it is also not working. Am I usig the correct command?
Thanks and Regards
Markus
SEGGER J-Link Commander V6.16f (Compiled Jul 3 2017 15:58:03)
DLL version V6.16f, compiled Jul 3 2017 15:57:26
Connecting to J-Link via USB...O.K.
Firmware: J-Link OpenSDA 2 compiled Feb 28 2017 19:27:57
Hardware version: V1.00
S/N: 621000000
VTref = 3.300V
Type "connect" to establish a target connection, '?' for help
J-Link>connect CORTEX-M4
Please specify device / core. <Default>: CORTEX-M4
Type '?' for selection dialog
Device>CORTEX-M4
Please specify target interface:
J) JTAG (Default)
S) SWD
TIF>s
Specify target interface speed [kHz]. <Default>: 4000 kHz
Speed>4000
Device "CORTEX-M4" selected.
Connecting to target via SWD
Found SW-DP with ID 0x2BA01477
Could not power-up debug power domain.
Scanning APs, stopping at first AHB-AP found.
Found SW-DP with ID 0x2BA01477
Could not power-up debug power domain.
Scanning APs, stopping at first AHB-AP found.
****** Error: Could not find AHB-AP to communicate with Cortex-M core.
Found SW-DP with ID 0x2BA01477
Could not power-up debug power domain.
Scanning APs, stopping at first AHB-AP found.
Found SW-DP with ID 0x2BA01477
Could not power-up debug power domain.
Scanning APs, stopping at first AHB-AP found.
Cannot connect to target.
J-Link>
Hello,
I have a problem with my FRDM-K22F Evaluation board. When I’m trying to debug with Ozone I get always this Messages
J-Link: Executing InitTarget()
J-Link: Connect Under Reset
J-Link: Connect Under Reset
J-Link: Executing InitTarget()
J-Link: Connect Under Reset
J-Link: Connect Under Reset
J-Link: InitTarget(): PCode returned with error code -1
This interface is not supported by the connected emulator.
Selection will be ignored by the DLL.
Connection failed
It doesn’t matter if I’m using the onboard JTAG adapter (flashed with the JLINK Open SDA Firmware) or if I’m using an external JLINK-Adapter (and powered the FRDM-Board with the K22-usb-connector). With Both Adapters I’m getting the same Error Message. I tried also SWD and JTAG as a target Interface. Makes no difference
What does the error-Message mean? How can I solve it?
Thanks and regards
Markus
Hello Niklas,
Thanks for the scripts. With this extension it is working with my board. It is setting the alternative Pin configuration for the trace pins, but still keeps the original
one:
I already tried to deactivate the old pins by extending your code:
void AfterTargetReset (void)
{
Target.WriteU32(0x40048038, 0xFFFF); // System Clock Gating Control Register 5 (SIM_SCGC5): Enables Clock for PORT A-E, TSI, LPTMR1, and enables software access to the Low Power Timer module.
Target.WriteU32(0x40048004, 0x00001000); // System Options Register 2 (SIM_SOPT2): TRACECLKSEL (Debug trace clock select) : 1 == Core/system clock
Target.WriteU32(0x40049030, 0x00000400); // Select ALT Mode 4 of Pin A12 (Trace_CLKOUT)
Target.WriteU32(0x40049034, 0x00000440); // Select ALT Mode 4 of Pin A13 (Trace_D3) and enable High drive strength
Target.WriteU32(0x40049038, 0x00000440); // Select ALT Mode 4 of Pin A14 (Trace_D2) and enable High drive strength
Target.WriteU32(0x4004903C, 0x00000440); // Select ALT Mode 4 of Pin A15 (Trace_D1) and enable High drive strength
Target.WriteU32(0x40049040, 0x00000440); // Select ALT Mode 4 of Pin A16 (Trace_D0) and enable High drive strength
Target.WriteU32(0x40049018, 0x00000000); // Select ALT Mode 0 of Pin A6
Target.WriteU32(0x4004901C, 0x00000000); // Select ALT Mode 0 of Pin A7
Target.WriteU32(0x40049020, 0x00000000); // Select ALT Mode 0 of Pin A8
Target.WriteU32(0x40049024, 0x00000000); // Select ALT Mode 0 of Pin A9
Target.WriteU32(0x40049028, 0x00000000); // Select ALT Mode 0 of Pin A10
}Which is not working, also resetting it in the Register-View of Ozone is not working, as the debugger is activating the original configuration immediately.
Regards
Markus