that the esp8266 spits out to the serial monitor? I tried decoding to find the hex value and that came back with 0F6D2 which is odd enough on it's own.
If you mean that you see strange characters when the ESP8266 start up then see Why does ESP8266 show 'Garbage' characters? - Everything ESP8266
What it prints is not very exciting
ets Jan 8 2013,rst cause:2, boot mode:(3,6)
load 0x4010f000, len 3460, room 16
tail 4
chksum 0xcc
load 0x3fff20b8, len 40, room 4
tail 4
chksum 0xc9
csum 0xc9
v0004f4a0
oh I get that reboot stuff a lot. the character I posted was from that line of stuff you get on every restart.
But as long as you brought it up, what is a room and a tail? ets is probably the date of something. rst is probably short for reset. the causes are googleable. boot mode, I'm not sure.
All I would really want is the last successful instruction in the source that worked. That would make all this easier.
I don't know what it means, just what it says
As to what you say you want, I can't make any sense of that either. What is it that you are after exactly ?
The instruction that caused the exception.
but the OP was what is this---> ے<---- looks vaguely arabic, but where is it from? As I said I get a line of this with every restart as in:l$ܞ|⸮$⸮|⸮l⸮#|⸮⸮⸮⸮⸮r⸮#⸮#⸮p⸮n⸮loN⸮⸮⸮cp⸮$r$rlp⸮n⸮⸮$⸮⸮cn⸮|⸮⸮⸮⸮b⸮⸮no⸮l⸮⸮l`⸮2Nn⸮ln{⸮⸮⸮ors⸮ p⸮N⸮r⸮ܜ⸮⸮⸮#o⸮|⸮c⸮⸮oN⸮⸮l ⸮eno⸮rdor⸮⸮⸮Nrel
Did you some how miss this:
What were the results when you ran the Exception Decoder?
1 Like
I did read that but there was nothing about the characters in particular. It was more of how the baud reflects crystal speed.
was not aware such a thing even existed. I will give it a try, thanks.
Let's go back to basic
When and where are you seeing the odd characters that you are asking about ?
when I click the serial monitor button, they are the first things that burst on to the scene.
I just got that running. EXACTLY WHAT I HAVE BEEN LOOKING FOR ALL ALONG--THANKS!!!
that's what I was referring to in the above reply. very handy tool.
Which above reply ?
the one about the exception decoder. that thing is awesome. As far as the weird characters, my suspicion is that a certain random string of numbers will, by accident, force the IDE to print some double byte characters to the screen. As to the mechanics of what is going on, I don't have the foggiest notion.
The reason for the "weird characters" at start up is complete explained at the link provided by @UKHeliBob:
yes, that said it was voltage and or the baud thing. but still somewhere the errant codes are being translated into characters that I have never seen, so I wondered how that is happening. What is triggering something to put these what I guess are double byte character set codes on the monitor screen.
from today
⸮⸮ gets translated to 2E2E 2E2E in hex by
I don't understand why you're obsessing over this "double character" thing. The answer is simply baud rate. If the transmitter is sending characters at one rate while the receiver is expecting them at a different rate, the results will be unpredictable. A different terminal emulator program from the Arduino serial monitor may display them differently. Who cares?
because I'm a curious person. I want to know why. Just like the Wright brothers, Edison, Tesla, those kinds of people.