Search Results

Please, can someone reply? The supplier just clarify that the display uses ST7789V2 and not ST7789V3 (indeed ST7789V3 doesn't support 16 bits that I use).

Actually I'm using emWin with a small 2.4" display with ILI9341 controller, used in 16 bits data mode. It works well. Now I have to replace the display with one from another supplier. The new display is quite similar, but integrates the controller ST7789V3, always in 16 bits data mode. Is it compatible with emWin? In the manual I read ST7789 and ILI9341 are controllers that share the same driver: GUIDRV_FLEXCOLOR_F66709. However the manual says a generic ST7789. What should I expect with V3 vari…

Anyway it's better to compare the old and the new string, because if they were equal, WM_InvalidateWindow isn't needed.

Do you confirm that this bug appeared for the first time in 61603 (6.16c)? Is it safe to call WM_NotifyParent() before TEXT_SetText()? Shouldn't it be better to call it after? Source Code (14 lines)

I experienced the same problem with v6.16c (NXP binaries), so this bug is present at least since this version. Unfortunately the last NXP emWin binary is v6.16c, so I can't upgrade. What do you think of this workaround? Source Code (10 lines)Writing this piece of code, another question arose. Is it possible to know the length of a text in a TEXT widget? TEXT_GetText() copies the text of a TEXT widget in a buffer, but I don't know how to size this buffer in advance. I think it should be nice to h…

I read somewhere in the forum that there was a bug exactly with TEXT_SetText() when the length of the text does not change. I think I encountered it. Could you give me more details of which versions are affected of this bug? I read that 6.18c fixed this bug. I noticed this bug on a simulator under Windows (SeggerEval_WIN32_MSVC_MinGW_GUI_V616.zip). I'm using it because my embedded platform is equipped with MCU from NXP and the emWin last emWin release is v6.16c. Is this version affected of this …

C Source Code (23 lines)Output is Source Code (4 lines)How is possible that TEXT widget area is not invalidated after setting a new text? Indeed I don't see any visible changes. If I call WM_InvalidateWindow() on the widget, the behaviour is correct and I see the new text in the TEXT widget. It's an oddy behaviour, because it may depend on the first text set during TEXT_CreateEx(). I create the TEXT widget with the following code: C Source Code (5 lines)If I change the text in TEXT_CreateEx() it…

From what I've understood after reading User's Manual of LPC546xx MCUs by NXP, internal Flash is organized of uniform 32kB sectors and uniform 256B pages. There's a command to erase one or more sectors and there's a command to erase one or more pages (that must be all inside a sector). In my project I'd like to have a bootloader at the beginning of internal Flash with a size of 20kB. So the application should start at address 20480=0x5000. I'm using MCUXpresso IDE and I think I've configured eve…

50116485 However we are testing ground connections. We measured around 20Vac between board ground and J-Link ground, before connecting them. I'm suspecting that the problem can arise when I hot-plug J-Link flat cable to the board. The board is supplied from an AC/DC with its metallic case connected to earth and the reference of its output +12Vdc is connected to earth too. The PC is a standard desktop computer connected to a UPS. I don't know why there's such a residual alternate voltage, most pr…

Quote from SEGGER - Fabian: “I highly suspect that this is connected to your hardware. ” Ok, but this happened on three different boards. If there's a problem on my hw, it is repetitive on multiple boards and MCUs. This isn't the first board we design, we don't explain what is happening. Quote from SEGGER - Fabian: “Does the same issue appear when using an evaluation board? ” Until now no, I have these issues only on custom boards. Anyway they are very similar to EVB, at least for SWD lines conn…

After some investigations, I found something interesting on SWDIO pin. When the probe is able to connect to the MCU, SWDIO signal goes high and low without problems: I can see 0V and Vcc on scope. On MCUs that are broken, SWDIO swings in a more restricted voltage range: for example from 1V to 2V. It seems SWDIO is broken inside MCU, but this happend THREE times! Is it possible that J-Link is responsible for this? Is it possible that a malfunctioning J-Link could apply a somewhat high voltage on …

Hello Fabian, I know it's incredible, but three times I experienced this problem on three differrent PCBs and MCUs: LPC54101, LPC54618 and LPC54606. J-Link returns the error "Could not connect to target", it seems SWD access is locked on the MCU. I don't know what's the problem is, but I'm starting thinking of the J-Link that could be malfunctioning (even if it works great with other boards and MCUs). I have the latest J-Link software and I tried to restart from a blank project, without any succ…

Quote from Fabian: “Usually such a Problem is connected to one of the three following points. The application 1) re-configures the debug pins as GPIOs. ” I think this is not my case for a simple reason. I can enter ROM Bootloader by keeping low one ISP bootstrap pin. When in Bootloader, my application doesn't run at all. However, even when the ROM Bootloader is active, SWD doesn't work (while on EVB I can connect through SWD during Bootloader). Quote from Fabian: “2) enables chip security (by ac…

I'm working on two different prototypes of two different boards with two different MCUs of the same family: LPC54618 and LPC54628 by NXP. Initially J-Link is able to make a good connection via SWD and I can download new firmware, debug and so on. However, it happened two times (the first with one board and the second on another board) that J-Link wasn't able to connect to the MCU anymore. In the first case, I mount a completely new PCB (with a new MCU) and now it is working well, but the origina…

Quote from SEGGER - Florian: “What you are describing is not a memory leak, but normal behavior of emWin's memory management. ” It was really a memory leak, because after some open and close the child window, emWin crashes for an out of memory error. However I found the solution, it wasn't a problem in emWin, I was creating the window two times, but deleting only one instance. Probably the sentence in the manual explains why GUI_ALLOC_GetNumFreeBytes() doesn't return the same number after one WM…

I create a child window (child of background window) that has a button. When the button is pressed, in the event WM_NOTIFY_PARENT/WM_NOTIFICATION_RELEASED I call WM_SendMessage() to send a custom message to main/background window. During processing this custom message (in the callback of background window), I want to call WM_DeleteWindow() to delete the child window. Is it possible? It seems it works, but after some tests it seems there are some memory leaks. I can't call WM_DeleteWindow() from …

I tried to erase a sector of 4kB with the following command: Source Code (1 line)But the tool says: No Flash bank within given address range 0xA0080000, 0xA0081000 I suspect erase command completely do ignore added flash banks specified in JLinkDevices.xml, don't it?

I'm using an edited JLinkDevices.xml to add a custom Flash bank (actually a SPI Flash connected to LPC1788): Source Code (6 lines)What's the behaviour of erase command of J-Link Commander tool? Does it erase only internal Flash memory of LPC1788 or will it try to use Flash Loader to erase the added Flash bank?

I'm creating a Flash Loader for a SPI Flash connected to a SPI peripheral of LPC1788. After issuing sector erase command, you can know when the erase is complete by polling busy bit in the STATUS register. How do J-Link know when a sector erase is complete? In FlashDevice structure there are two members: TimeoutProg and TimeoutErase. Does it mean that J-Link waits for this maximum timeout to know when the erase is complete? Another question. Should the function EraseSector() return only after th…

Ok Fabian, thank you for your reply. Quote from SEGGER - Fabian: “"savebin" does not use the Openflashloader, and therefore only works, the external flash is already initialized. ” This isn't fully correct. In my case the external SPI Flash can't be mapped into the native addresses of MCU. So "savebin" couldn't work even if Flash is initialized, because the reading must be done by a dedicated code.