KeepIS
![](uploads/KeepIS/Avatar_2023-05-26_112444.jpg) Guru
![](forum_images/4_star_rating.gif) Joined: 13/10/2014 Location: AustraliaPosts: 1688 |
Posted: 06:06am 29 Apr 2024 |
|
|
|
Just a bit of info in case someone else comes across this with a Nano board.
I received a few Nano boards today along with a breakout Board for a testing jig I want to make.
I tried to program one and it failed - tried the rest and all failed. Tried my existing units with old bootloader and same Ch340 and driver, all good.
These used the old boot-loader and CH430 chip, I knew that, which is fine. These were only a few dollars each and the board is really nice - the CPU and components are all correctly marked and as advertised. they are almost identical to the existing boards I have, the exception is these have an SMD semi (FET or TR) next to D13 on the underside.
The program error is "cannot set com-state for \\.\COM7", now that gives a hint to the problem, seems the Arduino SW programmer could not initialize the port for a baud rate change, or the response for same was invalid.
I tried a terminal program and connected to the Nano without error, so the port is fine, USB is fine no errors. If it was not getting a response to a port baud rate change or bootloader init, then I thought I would try and fool the bootloader by doing the following.
1: I set the baud rate to 9600 with the separate terminal program, connect and immediately disconnected from the board.
2: Hit program on the Arduino IDE - and it worked perfectly and verified - press program again and it has the same initial error.
So something wrong with the new boot-loader response in all of them.
Repeat Step 1 and it works again for one program verify loop from the IDE.
FYI - I'm using the correct CH430 driver version they expressly asked for in the info card that came with the boards. Even downloaded it and installed to verify. Have sent an question and info to seller (in AU)
I'll keep the board regardless as they are nice and they work perfectly once programmed.
EDIT:
Another possibility is a problem with the USB Nano reset bootloader sequence? It's obviously a problem with the boards - That extra SMD has me intrigued, must look at it when I get time. . Edited 2024-04-29 16:42 by KeepIS |