No output on serial console about zimodem HOT 8 CLOSED

ALREADY APPLIED ?! That's awesome!

However, your having troubles is not awesome.
My first question is whether anything happens when you type AT and press enter. Do you get the initialize message with the board info when you reset?

from zimodem.

ALREADY APPLIED ?! That's awesome!

They're literally the libraries you use in production, or at least that what's written inn the Readme lol

BTW yes, when I restart the board I get the usual board info at ~11kbaud on the arduino serial monitor

From the old computer side I can't write anything, on the arduino monitor side I can write but I get no response, I'll double check tomorrow just to be sure (it's 2AM here rn 😂)

Thanks for the reply have a good night/day!

from zimodem.

Hi -- I couldn't quite tell from your answer: you see the startup message on the old computer side I assume: it should end with INITALIZED and then READY, right? Is that correct?
I understand you are not able to type from the old computer side. What are your old computer flow control settings?
The debug serial side (115kbaud) isn't interactive -- it just sends debug messages. So that's not supposed to let you type anything.

from zimodem.

I just tried now (last time I tested this was a month ago) and this is the result:

If I send a message trough the arduino monitor i get no response.
If I write on the putty shell i get the led on the RX line to blink, but there are no characters drawn on the shell.
If I type blindly "AT" and press "enter" i get no activity on the TX line and nothing on the screen.

Please let me know if you need some more tests, also I wanted to say that I'm using putty with a serial to usb adapter so I can copypaste better and so I'm sure it's not fault of some finicky old software on a 386sx laptop with a failed floppy drive and a (replaced) failing hdd.

from zimodem.

Wow, so, hmm. It seems like UART 1 and UART 2 in my firmware might be mapping to the same physical serial port on your hardware. We may be looking at some incompatibility between your unit and the ESP32 libraries I use -- since I rely on those to keep this stuff straight.

Is it something different in the hardware, or something wrong with the libraries though? Well, one way to check!
If you'd like to try, please download my backup archive that contains the exact revision of the ESP32 libraries that I use, but it also contains a bunch of other related backup stuff for me personally.
So:

1. Find your esp32 arduino package libraries and archive them, in case this breaks something.
2. Download http://coffeemud.net:8080/ctcug/firmware/GuruModem-Zimodem-ESP32-DevBackup.7z
3. Extract the 7-Zip and pull out my own esp32 libraries from:
   GuruModemDevBackup\Users\Bo Zimmerman\Documents\Arduino\hardware\espressif\esp32...
4. Put my libraries where yours were. If you are not building in Windows, you may need to run the python scripts in tools to get the proper binaries for your OS.
5. Let me know if the behavior stays the same. If it does -- we may be looking at something unique about the hardware itself.

from zimodem.

I tried 2 different boards: one is those classic esp32 devboards that have a esp32-wroom-32 module soldered on it and the other is this thing https://github.com/LilyGO/TTGO-TS
One thing in common is the presence of the CP210x USB to UART bridge.
They both have the same problem as described before.
Also I have updated the project to the latest one on the repo as of yesterday and the problem has not changed.
Thanks for the libraries, but deleting the folder of the old ones and putting these newer ones didn't change the problem (at least it didn't break anything ':D)

I am using arduino in portable mode, so it doesn't mess up any other projects i need to compile and so I don't have problems while compiling with either esp8266 and esp32, I just need to keep the projects in different folders each with their own copy of arduino and libraries.
This means that I can zip the folder and directly send it to you if you prefer, so we can rule out any human error on the software side.

from zimodem.

Well, in that case, all that's left is to get ahold of similar hardware. That TTGO-TS seems way overkill .. if you can give me a grocery list and some instructions on your esp32 board, I'll give it a shot. I'm afraid I'm not a hardware guy, so giving me instructions like "get something sorta like X and then just hook it up to Y" will go absolutely nowhere with my brain. :( I can follow simple instructions though, and I own a soldering iron!

from zimodem.

I just looked up the pinout for the generic devboard and I've seen that there are "rx0" and "tx0" pins (where I was connected) and "rx2" and "tx2" that I totally didn't see on the silkscreen
Sure enough connecting the max3232 to those pins makes it work...
It's beyond me why the second board has only the UART0 pins exposed but whatever, would've been cool to send some info to the screen and use the built-sd adapter (and also maybe make the speaker do some tones :B).

Still, I am really sorry for wasting your time.
If you want/have the time please update the readme to add these suggestions:

A) downloading a fresh copy of arduino, creating a folder called "portable" in the arduino executable's folder so the changes made to the library are not system-wide
For posterity: from the zip you sent I put the content of the folder "C:\Users\Sonno\Downloads\GuruModemDevBackup\Users\Bo Zimmerman\Documents\Arduino\hardware\espressif\esp32"
in "folder-containing-arduino-executable\portable\packages\esp32\hardware\esp32\1.0.0"
(compiling worked first try after getting the path just right)

B) specify that you have to hook the max3232 (or whatever other ttl to rs232 conversion chip) to the UART2 port on the ESP32 side

I have now to check the code to see if it's possible to swap the 2 UART ports.
Have a good evening!

from zimodem.