Search results

Hello Yves, Thank you for your inquiry. Such an issue is not known to us. Did you edit anything in the project? It is configured to run out of the box. When changing settings make sure to follow the "Getting Started" from our AWS page step by step. Best regards, Nino

Hello Lance, Thank you for your inquiry. Such an issue is not known to us. Did the issue start right after installation or did you create a project and the issue appeared afterwards? Could you provide us with your emProject file and emSession file if you created a project? Could you attach the settings.xml as well which is located in the Embedded Studio user folder? After you attached the requested files does deleting the settings.xml and emSession file (if available) solve the issue? Best regar...

Hello, Thank you for your inquiry. What exactly is your setup? Do you want to program the device through an MCU with a flash loader? Or do you want to connect the SPI flash directly with J-Link and flash it that way? We offer solutions for both options. For the first one you would need to write a new flash loader for the MCU you are going to use if it is not supported already: https://wiki.segger.com/Adding_Support_for_New_Devices For the second option you can simply use JFlashSPI. A list with s...

Hi Mike, Thank you for the flowers Quoted I think you can close this case, as I'm sure I can get this all working once I get the scripts and FSMC interface setup properly, thanks again for your help! You are welcome. We will consider this thread as solved now. Best regards, Nino

Hello, Thank you for your inquiry. The documentation about the scanf and vscanf implementation in Embedded Studio can be found in the help section under <stdio.h> API Summary. An online version is also available here: http://studio.segger.com/stdio_h.htm You can also rewrite all API functions as they are defined as weak and can be overwritten by user code. Best regards, Nino

Hello, Thank you for your inquiry. Did you specify a registers file in your project settings? The registers you are seeing are the default Cortex-M registers. For device specific registers you would need to install the device support package and either create a new project where the project gets created from the device specific files or you can copy the registers file to your current project. More information about support package can be found here: https://www.segger.com/products/developm…gy/cp...

Hello, Thank you for your inquiry. Ctrl+J is the right default combination. Some Hotkeys are remappable. You can find the file to edit under File->Open Studio Folder->Studio Folder->/bin/keyboard.xml Before editing Embedded Studio must be closed and we suggest creating a backup of that file should editing go wrong. Best regards, Nino

Hi, We will consider this thread as answered now. To stay up to date on J-Scope releases we suggest subscribing to the J-Scope notification list: https://www.segger.com/notification/subscribe.php?prodid=201 Best regards, Nino

Hello, Thank you for your inquiry. For clarification, are you talking about the power supply of the Flasher itself or the possibility to supply the target device with power through Pin 19? In the latter case you can use J-Link Commander "power on" and "power off" for that. More information can be found in the J-Link user manual in section: Target power supply The same information can be found in the Flasher manual under the same section. Best regards, Nino

Hello Mike, Thank you for your inquiry. You have two options here. If you are using a Parallel CFI NOR flash and SPEAR 600 supports that all you need to do is tell J-Link where the Memory is located and initialize the pins for programming. More information can be found in the J-Link user manual (UM08001) in section "6.5 Setup for various debuggers (CFI flash)". To set the area command "SetCFIFlash" needs to be used. For all other cases our open flash loader interface can be used: https://wiki.se...

Hello, Great to hear that you are up and running again. Quoted This seems to mean that the microcontroller can never be erased and the board is useless! This is a pity. We suggest getting in contact with Infineon. They might know if the board is somehow recoverable. We will consider this thread as solved now. Best regards, Nino

Hello Niklas, Thank you for your inquiry. Such an issue is not known to us. Which iMX7 are you using exactly? Here is an overview of our currently supported devices: https://wiki.segger.com/IMX_Series_Devices Are you using custom hardware or an eval board? Best regards, Nino

Hello, Thank you for your inquiry. Such an issue is not known to us. Are you using custom hardware or an eval board? Does the behaviour change when using the GUI version of GDBServer? What Linux OS are you using exactly? Which GDBClient were you using? Could you provide us with a reproduction scenario and example project for a STM32072 eval board? We have the following available: - STM32F072B-DISCO - NUCLEO-F072RB Best regards, Nino

Hello, Thank you for your inquiry. Such an issue is not known to us. Which target device are you trying to program exactly? Here is an overview of iMX devices with native QSPI support: https://wiki.segger.com/IMX_Series_Devices Are you using custom hardware or an eval board? Best regards, Nino

Hello, Could you tell us what happens if you try to program the device again with J-Flash after it got into the "false" state? Do you get the same error again? Quoted If it works properly most the time, and can suddenly failed - and we must reprogram or erase it by Keil flash alghoritm - it means, it is not a HW setup/PCB problem. It might be a Flash problem - something latches - or your programming algorithm for that memory is not good enough. Not necessarily. You wrote that the Keil flash load...

Hello, Thank you for your inquiry. Such an issue is not known to us. Generally we do not provide support for older software releases if there are newer available. Could you update to the latest version and see if the behaviour changes? What is the serial number of the J-Link you were using for flashing? Are you using custom hardware or an eval board? If eval board which one? Could you provide us with the project file and hex file for reproduction? Best regards, Nino

Hello Milan, Quoted Yes, I am sorry. STM32F042F6. Ok, we retested with a STM32F042_Nucleo eval board. Attached is the successful connect with the on board J-Link. We suggest comparing that hardware design and see if you have missed some mandatory components for external debug probes to work. Last time we had a customer with a not working ST custom board it was due to some capacitor that was mandatory and he forgot to mount. The same suggestion goes for the NXP chip. What is different in the MCB1...

Hello, Thank you for your inquiry. The SDK is available and info@segger was the right place to contact. Usually this is sorted within a day but depending on the e-mail load response can be delayed. I will make an exception in this case and send you the download link per PM in this forum. We will consider this thread as solved now. Best regards, Nino