You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
for using escom on the Win10-console I did try sucessfully ansicon as
ANSI-escapecode-wrapper.
The new version of mecrisp-stellaris for the RPi Pico R2040 does also use a baudrate up to 921.600, so I recompiled escom with TDM-GCC-32
(had to add the new baudrates to /TDM-GCC-32/include/winbase.h)
Compile went fine and 921.600 Baud are now useable - maybe you will release a new version with your compiler?
Thanks,
The higher baudrates were not defined in windows.h. But all baudrates are allowed.
So now Escom will allow non-standard baudrates, although a warning is printed when using non-standard baudrates.
Thanks, The higher baudrates were not defined in windows.h.
but windows.h does "#include <winbase.h>" where I defined the baudrates (named CBR_) not these BAUD_ - so my version isnt showing the baudrate warning ;) [EDIT] Ahh - you did mean your version - which is also new :)
for using escom on the Win10-console I did try sucessfully ansicon as
ANSI-escapecode-wrapper.
The new version of mecrisp-stellaris for the RPi Pico R2040 does also use a baudrate up to 921.600, so I recompiled escom with TDM-GCC-32
(had to add the new baudrates to /TDM-GCC-32/include/winbase.h)
Compile went fine and 921.600 Baud are now useable - maybe you will release a new version with your compiler?
escom32_921k6.zip
The text was updated successfully, but these errors were encountered: