Search results
Search results 1-20 of 938.
Hello, To make sure the external keyboard issue is not a new one could you see if Embedded Studio V3.34 works? You can find it on the download page as well under button "Older versions". It should be only the 3.34a currently with the issue. If it is working for you with 3.34 then it will work again with 3.34b as well. Best regards, Nino
Hello Dominik, Thank you for your inquiry. Are you trying to debug eval or custom hardware? If eval which one? Can you connect to the chip using the J-Link commander? https://wiki.segger.com/J-Link_cannot_co…-Link_Commander Best regards, Nino
Hello, Thank you for providing additional information for a barebone setup. We will consider this thread now as solved. Best regards, Nino
Hello, Thank you for your inquiry. The 10M instructions in Ozone timeline is currently a hard limit which will be lifted in future versions. Unlimited is currently true for all code profiling, coverage, and instruction counter information. The timeline had to be capped due to careful resource management with that much trace data on the host PC. This is however not necessarily needed anymore and will be improved. Quoted Then a similar question is whether or not there is a history horizon on what ...
Hello, Thank you for your inquiry. Does a connect work with the J-Link commander? https://wiki.segger.com/J-Link_cannot_co…-Link_Commander Does a connect work with the isolator removed? Third party isolators sometimes have sub par coupling ICs installed which can lead to timing problems on the JTAG lanes. That is why we offer our own set of isolators which are guaranteed to be working with J-Link: https://www.segger.com/products/debug-pr…ators/overview/ Also the BGM11S is officially not listed a...
Hello Wilson, Thank you for your inquiry. When setting up the project how did you proceed? Did you follow the steps described in our Wiki? https://wiki.segger.com/How_to_use_an_ex…Embedded_Studio We looked at the project you supplied. There you are using the startup_ARMCM_GCC.S which is not compatible with Cortex-M0 but with Cortex-M4. To make your project build you will need to include a startup that is compatible to your external linker script and core. Unfortunately we do not supply such file...
Hello, Thank you for your inquiry. The issue is known and has already been fixed in the internal build: https://forum.segger.com/index.php?page=Thread&threadID=4986 A release is planned next week. Just to make sure your keyboard layout is also fixed, which one have you set? Best regards, Nino
Hello, Quoted The board is NXP-lpcxpresso54608. Ok great, we have the same board in house. Could you provide us with an example application to program to it for reproduction? A hex or bin file would be sufficient. Best regards, Nino
Hello, Quoted My problem is, that I am not able to upload a file to the imx6ull. The first textbox shows the download succeeded. The link to the wiki is only an information for the user that the CPU has been halted temporarily to enable programming. The article is currently being worked on, that is why you don't find any information there. Sorry for this inconvenience. We recommend halting the CPU manually before using loadfile for this device. So your commands would be: halt loadfile... Quoted ...
Hello Dave, Currently there is no option implemented in Ozone to delete a chip. Ozone will automatically erase and overwrite memory on the target if it is different from the application you are trying to debug/download. However you can use the J-Link Commander in parallel to Ozone and use the "erase" command there prior to debugging. Best regards, Nino
Hello, Thank you for your inquiry. To use an external debug probe with the CC13x0 LaunchPads some of the jumpers need to be removed first: https://wiki.segger.com/CC1310_LaunchPad After that you should be able to connect through the JTAG interface. Best regards, Nino
Hello Martynas, The J-Link Commander does not have such an option implemented. Currently there are no plans to add this. For this purpose we offer our customers the J-Link SDK:https://www.segger.com/products/debug-pr…ogy/j-link-sdk/ It gives you access to the J-Link API documentation which can be used to create such functions as you described. As an example project you get the J-Link commander source code so you could add this dumping extension to showemulist. Best regards, Nino
Hello Zhenyu, Good to hear. This thread will now be marked as solved. Best regards, Nino
Hello, Please do not reopen ancient threads. The setup are software and hardware wise not comparable. Your post will be moved into a new thread to discuss your exact setup further. This thread will be closed now. Best regards, Nino
Hello Dave, This looks strange indeed. Just retested it with the project from Wiki with ozone V2.56g and J-Link DLL V6.30k and line 34 was executed normally as seen in my previous picture. Try updating to J-Link software V6.30k and see if the issue resolves. As the previous issue was linked to "bad" wiring could you try setting trace to 1-bit trace? To access this option simply open the trace project in Ozone and go to Tools->Trace Settings... Here you can switch between different trace sources ...
Hello, The script that you are referring to is ancient and is no longer compatible with the OMAP-L138 initialization in the current J-Link software. We do not recommend using it for OMAP-L138. Please understand that we can't offer support for old JLinkScripts that are not provided through the official release channels. As there is little market interest for the L137 and our resources are currently booked with more pressing projects we will not be adding support for that device at this point in t...
Hello, Thank you for your inquiry. Such an issue is not known to us. Are you using custom hardware or an eval board? Does SWO output work with the non CL version of SWOViewer? Best regards, Nino
Hello, Thank you for your additional information. From J-Link perspective it should be sufficient to simply enable PCK3 and pass the PCK3 clockspeed to J-Link user a J-Link scriptfile. Functions SWO_GetSWOBaseClock() and SWO_EnableTarget() can be used for that. More information can be found in the J-Link user manual. All the remaining ARM specific ITM,DWT etc. init is already done by J-Link. We do not recommend interfering with that settings as J-Link negotiates the fastest possible SWO speed wi...
Hello Allesandro, Great to hear that you are up and running again. We will consider this thread as solved now. Best regards, Nino
Hello, We received no answer from the customer so we have no information if that has been resolved for Niklas. Best regards, Nino
