【MM32 eMiniBoard Review】2b: Collection of board problems found so far and suggestions for board modification

mig29

【MM32 eMiniBoard Review】2b: Collection of board problems found so far and suggestions for board modification [Copy link]

 

It is necessary to collect the problems found to avoid duplication:

(Board: eMiniBoard MB025 main chip MM32F0133C7P)

The problems confirmed so far are:
1. The virtual serial port of the emulator does not work (it should be based on the open source DAP emulator). It would be much more convenient if the emulator had its own virtual serial port.
2. The virtual serial port program in the Demo program: ..\MM32F013x_Samples\LibSamples\USB\USB_Virtual_COM, the official website cannot find its driver. I tried several methods found on the Internet (such as using S's to cheat), but all failed.

Suggestions for board modification:
1. The current demo program on the board makes the buzzer sound when powered on. It must be modified to: you can stop playing with a button (because not every customer can get the driver program right the first time, and when they are struggling, this "music" will become an annoying noise)

2. It is necessary to add a reset button on the board ( placed slightly to the left of the current silk-screen eMiniBoard string):

Because some programs (such as USB) do not have the meaning of single-stepping, you only need to download the program and then use printf to print out the log for debugging. At this time, it is annoying if there is no reset button. USB programs need to be reset and restarted to re-enumerate. Without a reset button, you need to repeatedly plug and unplug two USB cables, which will soon drive you crazy. (The emergency solution is to temporarily solder one yourself)

Additional notes:

Sometimes when Keil is reset, it will return to the following line of startup:
LDR R0, =__initial_sp ; set stack pointer
MSR MSP, R0

;;Check if boot space corresponds to test memory

LDR R0,=0x00000004
LDR R1, [R0]
LSRS R1, R1, #24
LDR R2,=0x1F
CMP R1, R2
Then it dies at the following line. You need to reset Keil again before you can enter main() .
BNE ApplicationStart

w494143467

The summary is very accurate. Is there any problem with ADC multi-channel acquisition?

freebsder

It's understandable that the product board doesn't have a reset button, but it's rare that the development board doesn't have a reset button?

mig29

Append it yourself:

A temporary solution for the lack of a reset button: Go to the Utilities page of Option, click Setting, and check "Reset and Run". It can be automatically run after downloading.

littleshrimp

I got my hands on this board today. Currently the emulator virtual serial port works normally and the USB CDC works normally.

If your problem is not solved, it is recommended that you install these tools

http://www.mm32mcu.com/download.aspx?cid=2547

mig29

littleshrimp posted on 2020-12-4 14:56 I got my hands on this board today. Currently, the emulator virtual serial port works normally and USB CDC works normally. If your problem has not been solved, it is recommended...

Thank you for your information. I checked and found that the simulator FW has been revised, but I also found a bug in the upgrade process: it may be that the upgrade program will check the FW version, but the new FW has not changed the version number, resulting in the inability to upgrade. . .

mig29

I downloaded the emulator FW on November 3rd, posted this post on the 4th, and then there was a FW on the 8th on the MM official website, but the version number did not change, it was still 1.65.

Then, the upgrade program should check the FW version, because the new FW has not changed the version number, resulting in failure to upgrade. . .

This is the FW downloaded on the 3rd:

This is the version from the 8th and cannot be flashed.

littleshrimp

mig29 posted on 2020-12-14 23:52 I downloaded the emulator FW on November 3, posted this post on the 4th, and then there was a FW on the 8th on the MM official website, but the version number has not changed, it is still 1.65. ...

mig29

littleshrimp posted on 2020-12-15 10:00

You probably got the board relatively late, and directly flashed the FW version released on November 8, so it was successful.

I have already flashed a version (October 21, ver 1.65), and the version information in the November 8 version is still 1.65. The upgrade program will check the ver information and cannot flash it in. . .

The original manufacturer cannot see this post, so I can only ask EEW to pass it on.