[National Technology N32G457 Review] 1. Brief review of the first power-on

yang377156216

[National Technology N32G457 Review] 1. Brief review of the first power-on [Copy link]

 

【Document preparation】

Before getting the development board, I wanted to search for all the information about the chip and board for this evaluation from various channels on the Internet, but I was helpless. I don’t know why National Technology did not provide enough resources to developers on the official website and electronic forums. The only way to get fragmented information is through the QQ group (unofficial technical support group created by National Technology agents, 877813702 ). What’s going on with such a closed development ecosystem? This is deliberately making things difficult for engineers! There is no way, so I can only feedback this "difficulty" to the event organizer. Fortunately, the EEW staff was quite helpful. Within 2 days, I got the official resource package and shared it in the forum in time. Here is a link for friends who are also in need: National Technology N32G457 .

After downloading the official resources collected by the staff, I took a preliminary look at them. The data package is relatively complete for developers. From documents to driver packages, to related tools and tutorials, it basically meets the necessary conditions for development. The style of the resource package is also relatively standardized, which is quite good compared to other domestic manufacturers.

[Unpacking]

On a cold rainy night, I received the N32G45XVL-STB development board from EEW. This really warmed my heart, and I excitedly opened the box. The box of the board is a bit big, which makes the things inside look a bit small and few. There is really nothing inside, an anti-static bag with a blue board + a MINI USB data cable. The product shipping label on the anti-static bag has relatively complete parameters, and a QR code is attached. You can directly scan the code to get the information data of the board in your hand. Take out the development board from the anti-static bag. A dark blue rectangular board fits in the palm of your hand. The 4 plastic fixing columns that come with the board make the whole board look more delicate. The only drawback is that the rough edges around are not polished clean, which is relatively rough and easy to scratch your hands. I hope the original manufacturer can improve this in the future.

【Power-on】

By consulting the schematic diagram and related information, I know that the development board already has a built-in CMSIS-DAP debugger, so there is no need to borrow an additional debugging emulator for development. This is very convenient, and the official host computer burning tool also supports this DAP tool. Since I am used to using MDK-Keil for development, I found the Keil pack of N32G457 in the previously provided data package and installed it, and prepared other necessary tools and environments for development. Connect the DEBUG USB port of the development board through the MINI USB cable for the first power-on operation. It is found that after the board is powered on, there is no other phenomenon except that the D4 green LED light is on. This experience is a bit unfriendly, which makes users question "Is the board broken as soon as I get it?" I hope that it can be equipped with a factory program such as a flashing light to give feedback after the board is powered on for the first time. Since the CMSIS-DAP tool was recognized by enumeration on the computer, a dialog box popped up to show that a new USB device was added. Then, the CMSIS-DAP device could not be found in the device manager. There was only a composite device and a CDC device type, but according to past experience, there should be a DAP. I found the official library routines and opened an IORemap project. In the debug option in the project options, I selected CMSIS-DAP. After clicking it, I found that the relevant SN number could not be recognized, and naturally the chip ID of the development board could not be recognized. It seems that there is a problem that the CMSIS-DAP device could not be found in the device manager after the previous enumeration was successful. After repeated uninstallation and re-enumeration, Keil still could not recognize the available debugger. I was very sad. Is it impossible to use it? Well, the onboard debugger cannot be used, so the only option is an external debugger. Fortunately, the design of the board is friendly and supports jump caps to choose whether to use an onboard or external debugger. Connect the J-Link to the development board according to the silkscreen markings (GND / SWDIO / SWDCLK three wires are enough), select J-Link as the debugger in Keil after power on, select the M4 core device in the pop-up device dialog box, the chip ID number is recognized normally, and the compilation and download can also proceed normally. Well, that's it, from now on, I can only use the external J-Link to do development and debugging.

[Some findings after power-on]

In the .s file, a sentence is missing, which makes it impossible to use Keil's visual configuration tool normally. Just add it as follows:

///<<< Use Configuration Wizard in Context Menu >>>

In the lighting experiment, LD2 (PB4) could not be lit normally at first. The reason for the failure was that PB4 was not reused as a normal IO. You need to first familiarize yourself with and debug the IORemap in the routine and check the corresponding DS manual to find the problem.

Since N32G457 is claimed to be a pin-to-pin product with STM32F103, I checked the pin association and found that the pin definition is exactly the same as that of the STM32F103 100pin product, even the NC pin is the same, but the function reuse definition is not completely compared. I will make a corresponding comparison when using related modules later.