My traget mcu is M258KE3AE NuTool-LCDView version is v1.05.0004 and NuTool-PinConfigure version is V1.27.0001.
I generated pin setting by using used NuTool-PinConfigure. I found the save file's sub-file name is ncfg, not cfg, so it can't be read by NuTool-LCDView. Please fix this bug. Thanks.

Nu-Link2 is lightning-fast in Keil, but I'd really prefer a more modern development environment than µVision, especially for day-to-day software work. Something capable of hosting a gdbserver is a must.

Is there work underway in improving OpenOCD performance for the Nu-Link? I just bought a Nu-Link2-Pro, and it's essentially unusable for day-to-day development with OpenOCD (it takes 42 seconds to flash the lwIP demo to my M487 NuMaker board)

When I switch the Nu-Link2-Pro over to the DAPLink firmware, it takes less than 10 seconds, which is an amazing improvement! I wouldn't mind permanently switching to DAPLink, but Nuvoton doesn't appear to offer "generic" DAPLink firmware that works on the NuLink2-Pro; the firmware images are all target-specific.

Worse still, Nuvoton only has four or five MCUs supported in DAPLink right now. I have projects that range from old NUC100-based designs to the newest M032 and M33 offerings, and I purchased the Nu-Link2-Pro thinking I could use it on all of those projects.

Until this gets sorted out, I'm stuck using my Segger J-Link / J-Trace — those are great tools, but I'd really like to be able to use the built-in debuggers found on all the NuMaker boards I've been acquiring. They need a huge improvement in performance first, though.

It would be nice to generate Device-Tree file, based on the selected pin mode and peripheral.

I'm trying to reconfigure the Nu-Link2-Pro to become a CMSIS-DAP by setting CMSIS-DAP=1 in the NU_CFG.TXT file, but the setting never sticks. I've tried ejecting the drive in Windows to force any pending writes to complete, and that doesn't help either. I've tried setting other things in the config file and they also fail to set.

I've tried it on Windows 10 and Windows 11, and I've tested every firmware version in this repo that has this feature (from revision 7174r to the latest version).

Also, I noticed that Windows thinks the file is "read only" — I have to clear that checkbox to be able to save the file. I'm not sure if that has anything to do with it.

It's impossible to configure pinout for LCD connection

I Building TF-M code,and Flashing Image with Nuvoton NuLink Tool,NuMaker-PFM-M2354 board supports on board ICE called NuLink. Connect NuLink to PC with USB cable and using NuLink Command Tool to flashing the image.

The commands are as follows:
NuLink_M2354 -C
NuLink_M2354 -E ALL
NuLink_M2354 -W APROM ./build/bin/bl2.bin 0
NuLink_M2354 -W APROM ./build/bin/tfm_s_ns_signed.bin 0 0x20000
NuLink_M2354 -W NSCBA 0x70000

when run command " NuLink_M2354 -W APROM ./build/bin/bl2.bin 0", cannot execute,To quote the following wrong:
$ NuLink_M2354 -W APROM ./build/bin/bl2.bin 0

ERROR: Failed to Parse the Flash Algorithm!!! <<<

******************** Execute operation ending ********************
CAxf: open file erro

May I ask why?

Rather than using the "Generate Code" feature, ClockConfigure and PinConfigure should have a button to allow the user to copy the register init code, as plaintext C code, to the clipboard so that they can paste it into their project.

Right now, it's rather clunky to use and integrate these tools into a project. Both ClockConfigure and PinConfigure have a "Generate Code" feature that will create a series of directories and separate MyProject.c source files that both contain a void SYS_Init() method with the generated registers. However, these files obviously can't be used unmodified, since the method names are identical, thus the user has to manually combine the code in these methods into their own project tree.

It seems like it would make more sense to just copy the contents of these generated SYS_Init() methods directly to the clipboard so the user can paste it into their own project.

Loading any saved configuration does not work:

Right now, PinConfigure is basically just for wiggling the MFP bits to enable peripheral pin muxing. It would be nice if the tool added GPIO pin mode configuration, which would generate lightweight C code to program all the GPIO registers en masse.

When you click on a pin, you could either select its special function (say UART0 TX or PWM1), but you could also choose the GPIO mode. An additional view on the left would show all the configured GPIO pins and further allow you to select their pin mode, slew rate, interrupt, etc.

I know the Nuvoton BSP has methods for doing this, but it seems more logical to have this done as generated init code, which is similar to other platforms that use code-gen tools. It is very common for an EE who designed the board to configure all the pins for the software engineer before handing off the project, so doing that in the GUI tool would be fantastic.

In both the ClockConfigure and PinConfigure tool, hitting Ctrl-S does nothing, and hitting on the "Save" icon always invokes a file chooser. These apps should remember the file that was opened and when the Save button is pressed, write to that same file. An alternate "Save As" button could be implemented to change the file path.

Additionally, Ctrl-S should bind to this "Save" command, as it does in 99% of other Windows applications.