Search Results
Search results 1-10 of 10.
This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.
-
I have solved the problem. Use CubeMx generate the TureStudio project with the same configuration of the your keil project. Then replace your the port.c and portmacro.h files with the TureStudio generated files in your keil project. Because SES use gcc compiler and TureStudio also use gcc, so the ported file can be used in SES.
-
No update for this problem, I got the same problem now. How can I fix it?
-
Thank you for the help, it's ok now.
-
I can't find the "Target | Connect | SEGGER J-Link" options in my studio, only "Target | Connect Simulator", what't the problem ?
-
When I connect Rttview to the device, the device stopped. I have checked my code, there's no any protection that stop jlink connect. My chip is stm32f091rc, can you try to reproduce it by yourself. I have tested that the simplest project got the same problem. And another question, Can't you find the any hint from my rtt viewer log?
-
Any update?
-
the is the log of rttviewer with J-Link 5.10n. My PC os is windows 10 64bit. I create a simple stm32f091rc project with stm32cubemx, add rtt source code manually. rtt works well in keil debug mode. But if I use rttviewer standalone, the jlink can't find the rtt cb. Seems like jink can't readback memory data from the chipset if I use rttviewer standalone.
-
I have tried that version, still can't get any output, v500l gets no output neither. In keil debug mode, the rtt works well. Only when I use rtt viewer standalone, it jlink can't locate the rtt cb.
-
My target is stm32f091rc, system is windows 10. I have tried the new jlink software but still can't get any output with only RTTViewer. If I set the RTT cb address when startup RTTViewer, I still can't get any output. When I use SWO, it's well to use JLinkSWOViewer as standalone. Is it impossible to use RTTView standalone, i.e, without in keil debug mode?
-
When I am in Keil Debug mode, the RTT work well. But If I start JLinkRTTViewer without in Keil debug mode, then the JLinkRTTViewer can't find the RTT CB, and it will find it again and again.Below is some jlink log: SEGGER J-Link V4.98e Log File DLL Compiled: May 5 2015 11:00:52 Logging started @ 2016-02-23 15:34 T0474 000:000 JLINK_OpenEx(...) Firmware: J-Link ARM V8 compiled Nov 28 2014 13:44:46 Hardware: V8.00 S/N: 286370559 Feature(s): RDI,FlashDL,FlashBP,JFlash returns O.K. (0270ms, 0270ms t…