Esp8266_deauther: Serial Interface Messy Outputs :

[ExploiTR]

Using the serial interface and it just works as fine as it's programmed to do. But, at first start of 8266 I'm getting some messy messages in the console which is quite disturbing. Can you tell where the problem exist? I'm getting other messages in human-recognisable string as usual

@spacehuhn @spacehuhn @spacehuhn

Like this :

��ʼ���pc�&�
�ak�����p�Q�
�$�
�
�����L���Qr����+����6�>/P=K��U}���g| ����6�?B�`o������ld�W�r8Z��y*^�}W���
�y��dي���$א���R����嵢�AyH��X���
��5
    ����w�~����
�F8�k�0��� m������v�P�?>���Y�   �
Oy���oz3�3����S@�,�4)��7�
��stce����"^)�? �9�������¿��?������{q�\�)wR�]�
���[`��@�B�`��݈��/Z�`��be�
    ���������@��������C�\� �A>���3[�����Ek���C5$�  ��n~m�F(��9����b��
�sN��fYd�����
O���A~��d�����W��
�4�����F���j[����ӡ��k�ٲ����9���)�q�
    �b�|~&VCoL25k�(jN�,_��A�} Aۃ��o������;U��qw�y0���<�QLj����Xݤ�C>Lidk���YwR�^���P�֒��mAg�s5������
�
�B|�-����   �
    |g�w!'�1� �C
���

[bradanlane]

This looks like a mismatch between your Arduino IDE serial monitor settings and the code running on the ESP8266.

Follow this wiki page to insure you have the correct settings:

https://github.com/spacehuhn/esp8266_deauther/wiki/Serial

[ExploiTR]

both are set to 115200 :crying_cat_face:
flash size 4M(1M spiffs) [I've verified it with custom sketch]
Freq : 80MHz Mode: DIO Cpu:160

And, everything other is working fine like, sysinfo or scan

[ExploiTR]

@bradanlane and one thing to check , even spacehunn himself is receiving this (Collected from the wiki) : -

@spacehuhn

[spacehuhn]

@ExploiTR @ExploiTR @ExploiTR that is normal @ExploiTR

[EMLGaming]

is it fixed @ExploiTR @ExploiTR @ExploiTR @ExploiTR @ExploiTR ?

[ExploiTR]

@spacehuhn @spacehuhn I'm not telling it a bug/feature or anything else. I want to know which line of the program is making this output, will you please tell me?

If it's not a feature without which it will totally stop working, I'll remove that line and shall then re-compile. @spacehuhn

[jLynx]

None, it's part of the chip itself @ExploiTR so you cannot remove it. It's actually readable if you set the console to 9600 but then you won't be able read the actual messages from the deauther code

[ExploiTR]

Really? @jLynx But, when I use a simple sketch it doesn't happen.

But, in which logic you're saying to set it to 9600 I don't understand. The code itself uses Serial.begin( 115200 );

[jLynx]

Yes but the kernel is 9600. Like I said above. It's not in the code

[ExploiTR]

@spacehuhn If you can help please do.

[spacehuhn]

I can't

[ExploiTR]

Aaah, I found that the problem is specifically immutable. It's coming from the cp2102 (might be). Anyway thanks for the support. It took a large time to make it understand :trollface:

Can you tell me @spacehuhn @spacehuhn , if I use Arduino with the ESP12 will it also give those messages ???

[jLynx]

All ESP devises print out those message.

On Mon, Jun 25, 2018, 10:23 PM Pratim Majumder [e-mail]
wrote:

Aaah, I found that the problem is specifically immutable. It's coming from
the 2102 (might be). Anyway thanks for the support. It took a large time to
make it understand [image: :trollface:]

Can you tell me @spacehuhn https://github.com/spacehuhn @spacehuhn
https://github.com/spacehuhn , if I use Arduino with the ESP12 will it
also give those messages ???

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/spacehuhn/esp8266_deauther/issues/901#issuecomment-399904554,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEML-yZO_2l9E59BmF8Ep_Vu3mn7RgJIks5uALoSgaJpZM4U1OOH
.

[ExploiTR]

:crying_cat_face: :cry: :sob: :no_entry_sign: Oooops..

[spacehuhn]

As jLynx said:

None, it's part of the chip itself @ExploiTR so you cannot remove it. It's actually readable if you set the console to 9600 but then you won't be able read the actual messages from the deauther code

When the ESP8266 boots it's printing with 9600 baud. That is part of the bootloader I guess. You can't just disable that. Then it's switchting to 115200 baud because I specified that in the code. There's nothing more to it. It's not a bug.