Search Results

I am just curious: What happens if you specify the control block address manually, will it work then ?

Quote from pruesch: “fifo-style display might be a solution? discard older events to enable an endless live view.” Sounds good. Is this a feature already implemented, or you just shared your idea for a solution? I went through the user manual, and found nothing relevant to this. Thanks!

Hi! I'd like to kindly ask if in near future the limit of 1 million events will be lifted ? Thanks so much for the great tool!

Hi! I was always wondering, does the Jlink Base version contain a license for the J-Flash SPI? My understanding is, that J-Flash is not working with it, but how about the SPI-flash programming feature? Thanks!

Great! I am glad I could help.

Hi! I'd like to point out a bug in the latest V2.34 Sysview recording code: line 1161: C Source Code (1 line) Should be: C Source Code (1 line) Because the SEGGER_SYSVIEW_GLOBALS does not have a UpBuffer member anymore.

Apart from the different name in the drop down box, what is your problem? Keil may have renamed their option, and that's all. Which Segger debugger do you intend to use? Does it work, or not?

Quote from SEGGER - Erik: “ J-Flash will not use more then 192KB so this will not make any differences, but you are right. We will correct this accordingly in future versions. - Erik” This is actually correct. ST misleads its customers by saying the MCU has 256 Kbyte SRAM. In reality it has 192Kbyte SRAM starting from address space 0x20000000, and another additional 64Kbyte at 0x10000000. Notice, that they are on a totally different addresses. To utilize the 64Kbyte SRAM (which is called CCMRAM)…

The on board RAM should be sufficient to drive a 240x320 display. But take note, that it does not have 256KB RAM. It has 192 Kbyte Ram from the address: 0x2000000 And it has an additional 64 Kbyte CCMRAM, which is at address: 0x1000000 If you want to take use of the CCMRAM, you will have to modify your linker script. Also take into account, that without double or tripple buffering, you'll have a flickering display. You'll be able to use emwin's memdev feature, but it makes things a little more c…

To rotate the screen you need to set the correct X and Y physical resolution. Here is my GUIDRV_stm32f429i_discovery.c Take special attention to C Source Code (2 lines) and C Source Code (15 lines) Although I modified it here and there, a quick diff should show you what to do.

Thanks for the quick response! Guess then I'll have to bulk up my memory, or simply write my own skinning routines, which use memdevs manually. (I've already managed this, it just seemed too complicated tough ) Cheers!

Hi! If I set the WM_CF_MEMDEV flag for a window either at creation, or afterwards using the WM_EnableMemdev() function, then as far as I understand the Emwin driver will try to use memory devices to avoid flickering. Although it is not clear what will trigger the GUI_MEMDEV_CopyToLCD() in this case. What I am trying to do is to set up the Vsync interrupt to start copying from the Memdev to the LCD controller. I know I could use multiple buffering to avoid flickering, which is well explained in t…

Stefano: Make sure you have the Initial Reset and Halt option not set. See attachment.

It depends on your debugging environment. As a matter of fact, you should consult them. But the Jlink is capable of attaching to a running target, In the IAR for eclipse plugin for example you have something like you see in my attachment.

The Jlink edu does not have a license for the J-Flash.

As far as I know, the Cortex M0 series does not have SWO.

Thanks a bunch! Seems then I will stay with the channel 0 possibility. But still, very nice to have. The RTT-Logger sounds very promising as well. I'll keep myself updated. Thanks

Hi! I just stumbled upon Segger's RTT implementation. I am really impressed with it. There is only 1 question: It mentions that there is an opportunity to have multiple channels, aka. multiple up/down buffers. But the J-link RTT Client does not seem to read from it. What is the intention of having multiple buffers then? SEGGER_RTT.c says: Source Code (1 line) So I reckon there is some API to address the debugger hardware to read out the other buffers as well? Thanks!