Go Down

Topic: Problem with COM port. Help (Read 710 times) previous topic - next topic

Shtalker

1. Sketch:
void setup() {
        Serial.begin(115200);
        Serial.print("Test");
}

void loop() {

}

2. Drivers updated
3. Port speed tried different (9600 and 115200), in the port settings is also changed.
4. IDE v 1.8.9
5. Tool > board>arduino nano and Tool > proccesor>atmega328p(old bootloader) (though I bought cost UNO but not on another works)
6. Arduino buy on aliexpress in Wavgat store

Problem:
The port monitor displays - xxx?xx?
Help pls!


DrAzzy

#1
Apr 08, 2019, 08:14 am Last Edit: Apr 08, 2019, 08:15 am by DrAzzy
The wavgat boards have lots of issues - they actually use a different processor that isnt quite a clone of the 328p. I think they have a different clock speed from standard uno too (the cause of your current problem)

Suggest avoiding that brand like the plague.
ATTinyCore and megaTinyCore for all ATtiny, DxCore for DA/DB-series! github.com/SpenceKonde
http://drazzy.com/package_drazzy.com_index.json
ATtiny breakouts, mosfets, awesome prototyping board in my store http://tindie.com/stores/DrAzzy

pert

I think there was a report of needing to use 1/4 the baud rate in Serial Monitor as in your sketch. Try uploading this code:
Code: [Select]
void setup() {
        Serial.begin(38400);
}

void loop() {
        Serial.print("Test");
        delay(1000);
}

and then set the Serial Monitor to 9600 baud.

Let us know whether that works or not.

Shtalker

#3
Apr 08, 2019, 01:56 pm Last Edit: Apr 08, 2019, 01:59 pm by Shtalker
I think there was a report of needing to use 1/4 the baud rate in Serial Monitor as in your sketch. Try uploading this code:
Code: [Select]
void setup() {
        Serial.begin(38400);
}

void loop() {
        Serial.print("Test");
        delay(1000);
}

and then set the Serial Monitor to 9600 baud.

Let us know whether that works or not.
You are a genius! Thank! And what's wrong with my board?
Topic can be closed

pert

I believe what's wrong with your board is that WAVGAT is putting LGT8F328P microcontrollers on their boards which have been re-labeled as ATmega328P. I don't know who did the re-labeling, but there's absolutely no doubt WAVGAT knows their chips are no ATmega328P because they link from their official product listings to a specialized hardware package that is for the LGT8F328P. Even though they know this, WAVGAT clearly advertises these boards in the product as using ATmega328P and nowhere on the product listings do they mention that they are LGT8F328P so this is definitely a very unethical company.

Although not made by Atmel/Microchip, the LGT8F328P was designed to work very similarly to the ATmega328P that is used on the popular Arduino Uno, Nano, and Pro Mini boards. However, there does seem to be some differences that are causing the baud rate mismatch you encountered. You might try using this hardware package, which is essentially the one provided by WAVGAT, but with some serious bugs fixed:
https://github.com/ericvb/Arduino-WavGat-Drivers

There's another hardware package for the LGT8F328P that has been reported to be better than the one at the link above, even though it's not designed specifically for the WAVGAT boards:
https://github.com/LGTMCU/Larduino_HSP

I don't have any boards with LGT8F328P yet so I haven't tried either one out.

Go Up