Search Results
Search results 881-900 of 982.
This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.
-
Hi, Thank you for your inquiry. Could you please provide us with the serial number of the Flasher you are using and explain to us in which exact setup you are using it? Is it possible for you to provide us with a .dat file this is reproducible with and one with which everything is working as expected? Best regards, Fabian
-
[SOLVED] How to exit "debug mode" on Cortex M3 (EFM32GG290F1024) using J-Link GDB on Eclipse IDE?
PostHi Richard, This cannot be accomplished with eclipse, but you could use J-Flash for it. This requires the reset pin to be connected to the debug interface of the J-Link. In J-Flash, there is an option to start the application via reset pin after downloading the application. All information on how to use J-Flash and how to set the required option can be found in the J-Flash Manual (UM08003). Does this answer your question? Best regards, Fabian
-
[SOLVED] How to exit "debug mode" on Cortex M3 (EFM32GG290F1024) using J-Link GDB on Eclipse IDE?
PostHi, We are still not entirely sure what you want to do. From what we understand: You want to use the J-Link to get to a certain point of your application. Then you want to end the debug session and have your program run from this point to (for example measure power consumption) without the debug logic being enabled. Is that correct? This is currently not possible with J-Link. We see two possible ways to get what you want: 1) Measure the Power consumption from a certain defined point, with and wi…
-
Hi, Thank you for your inquiry. Unfortunately this device does not follow the ARM specification, because it has a high CPU speed. It is the same problem as with the ATSAM70: wiki.segger.com/ATSAME70 We will implement this natively for the SAM50 devices as well, in the future. If you need it before then, you will have to set up your own J-Link Script file. Please find further information about this in the J-Link Manual (UM08001). Best regards, Fabian
-
Hi, You are welcome! Good to hear that everything is working as expected now. Best regards, Fabian
-
Hi Victor, Thank you for your inquiry. It looks like you are writing to 0x00000000, not to 0x10000000. Are you trying to download a .bin file? If so, you will have to add the starting address of where to download the file as well: Syntax: loadfile <filename> [<addr>] Example: loadfile %pathToFile%\somedata.bin 0x10000000 If this does not solve the problem: Could you please send us a screenshot of the full commander output? Could you please send us a J-Link log file? How to enable: wiki.segger.co…
-
Hi, Thank you for your inquiry. I think there is a misunderstanding here. J-Flash is not able/supposed to program RAM. Also, what ever is written to the RAM, will be lost after reset anyway. It looks to me like you have a memory dump (.hex-file) and want to program the application in it to your target. The RAM data of the memory dump was written from the target application which is placed in the flash area. Therefore, it should not be necessary to program the RAM, since it will be written by the…
-
Hi, Thank you for your inquiry. Such an issue is not known to us. Could you please tell us which XPlained Pro board you are referring to? There are multiple boards with that name. Could you please send us a screenshot of the full J-Link Commander output? Could you please send us a J-Link log file? How to enable: wiki.segger.com/J-Link_DLL#Enable_J-Link_Log_File Best regards, Fabian
-
Hi, Thank you for your inquiry. Such an issue is not known to us. Could you please tell answer the following questions: 1) What device are you trying to get data from? 2) Do you get RTT output, when using a local setup (using RTT Viewer on the same PC as the J-Link is connect to, without Remote Server)? 3) Do you use custom hardware or an evaluation board? In the latter case which one? If custom hardware, do you experience the same problem on an evaluation board? 4) Could you please send us a sc…
-
Hi, Thank you for your inquiry. Such an issue is not known to us. Does this behavior also appear when using the newest J-Link Software and Documentation Pack version? You can download it here: If so, could you please verify if the target was successfully programmed and running after executing the script? Best regards, Fabian
-
Hi, Thank you for your inquiry. Such an issue is not known to us. Do you use custom hardware or an evaluation board? In the latter case which one? If custom hardware, do you experience the same problem on an evaluation board? Could you please send us a J-Link log file? How to enable: wiki.segger.com/J-Link_DLL#Enable_J-Link_Log_File Could you please erase the target via J-Link Commander and tell us if it works?: - Open the J-Link commander - Connect to the target - Write "erase" to erase the dev…
-
Hi Pawel, Sorry for the delay in response. We were able to reproduce the issue and are looking into it right now. Best regards, Fabian
-
Hi, Thank you for your inquiry. We tried to reproduce the issue. On the BCM43907 / CYW43907 WICED kit everything is working as expected. As we also answered your questions in our support ticket system we will consider this case as closed now. Best regards, Fabian
-
Hi Johannes, Sorry for the delay in response. We recently had a customer who had a similar problem. According to him the problem was caused by some switches on the evaluation board, which were not set correctly. Could you please check this? Did you contact Hilscher support? They might also know something about this. Best regards, Fabian
-
Hi Thomas, Thank you for your inquiry and sorry for the delay in response. We are able to reproduce this. Thank you for making this known to us. We will see if we can find a solution for this that works out of the box. As a work around you could write your own script where you implement the solution provided in the article. Best regards, Fabian