-
-
Notifications
You must be signed in to change notification settings - Fork 365
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ATMEGA32U4 ESP8266 - Steps to be followed #30
Comments
Can you provide more information about the board you'd like to use? |
Hi @cnu77, Hi @spacehuhn Maybe you @spacehuhn can help me to look at the right spot. I dont know where to look at. |
Thanks @alican
I tried both the links. As I am new to these h/w parts, its difficult for me to find even the correct pins. I tried to hold the two circled spots together using a pin header, again it fails with the same error. I guess this has something to do with the basic config like Drivers. But Windows 10 do not even tell if there is any error. When I connect, I can see the WiFi part can be connected from my mobile. So, I guess the WiFi part is working, but I am not sure if the same WiFi part is deducted by my Laptop or not. Also, I am not sure if the GPIO0 and GND are already connected (hardwired) or not as there is no mapping diagrams. There was a link but seems to be broken. Fingers crossed. |
Now, I tried this video https://www.youtube.com/watch?v=G-Z2rf_AN-c I followed the steps.
Now, I can connect to the WiFi Duck with password quackquack. But, I cannot run the script. Nothing happens. |
I have the same issue the old wifi_ducky works but the wifiduck doesn't. With the wifi_ducky I can run ducky script only in I gues the US layout. For the SD card on the CJMCU-3212 I don't know if you can use it and why I didn't test it. But after flashing the ESP8266-12e (I belive it's this model) you must re flash the arduino leonardo with this script: But this works only with the "old" version wifi_ducky not with this one. |
After checking the repo page I just realise the layout of the wifi_ducky is:
and the wifi_duck use:
If we refer to this picture and look at the wiring we use the wifi_ducky and not the wifi_duck so we need to adapt the code if it's possible.... |
Did anyone figure this out yet? |
I'm also waiting for progress. I'm sad that I can't use the board. I bought it just to play with it with wifiduck. |
Please share if you've found the necessary modifications to the code for this particular board. |
You have to use this repo because of the wiring of the PCB. For the moment you can't use the SD card and we are stuck with the us layout... |
Yes, i know the old version works fine. I even managed to change the layout but i would really like this updated firmware. To change the layout, you just need to modify the code in keyboard.cpp according to your own layout. File is located in C:\Program Files (x86)\Arduino\libraries\Keyboard\src As far as i know, the SD card can only be used to store scripts. It's pretty pointless since they can already be stored in SPLIFFS. Using it as a mass storage would be awesome, but i highly doubt it's possible due the contruction of the board. |
If you look at the code you will find that it's impossible to have the new functions on this board it use something like master slave between the ESP8266 and the Arduino (ATMEGA32U). The CJMCU-3212 is not plug like this like I mentioned in my last posts... The ESP have more space than the arduino so you can reprogram the keyboard function and add some layout but the arduino will not have enough space ... If you succeeded I need to take a look at it because I just add the mouse and sd card option and my memory is almost full. |
WifiDuck is using I2C protocol, that is available on specific pins. If you take a look at the schematic of the CJMCU-3212 board, you can notice that these pins of Atmega32U4 are available as header pins. On Esp12-F these pins are not connected to anything but they're big enough to easily solder them. So if you have a soldering iron, you could solder these 2 connections yourself. Edit: In config.h you can uncomment |
@michalmonday |
Not really a hero:p. It appears that someone already made an issue about using serial. Btw I just tested it (I don't have CJMCU-3212 but I have similar board that connects Atmega32U4 and Esp8266 using "Serial1" port of Atmega32U4). That's what I did:
|
It worked! Thanks! :)
I had the same problem and your solution worked for me. But I changed just the position because |
Were you able to test this solution on the CJMCU-3212? |
Yes. it works on the CJMCU-3212 and I run successfully a script. |
does the multiple keyboard layout are usable ? You talk about adding the |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I follow your steps the keyboard work but not the layout with the command LOCAL.... So the big purpose to get this version over the wifi ducky is gone... |
I forked the original repo (wifi_ducky) and added some functions.The website have a similar look to this project (WIFIDuck) and the sdcard can be use to store duckyscript. I store them with the extenxion .txt. |
Sorry the LOCALE with the layout name in CAPITAL (LOCALE FR) work I will check if I'm able to add the function to execute script from the SD Card! |
I'm not sure if it will be possible because after I added the SD function the space left for the variables in the memory are over 100%... |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Hello! This helped me perfectly with the CJMCU-3212. As @michalmonday says I have just edited "#define SERIAL_BAUD 9600" AND "Serial" in the "Protocol" tab instead of "I2C" This was my experience running WifiDuck with the CJMCU-3212 |
Hello you get a yellow mensaje that "Internal Conecction Problem" in yellow color idk why. |
I have the ATMEGA32U4 ESP8266, which has both the Microcontroller part and the WIFI part in a single board. How do I use these scripts in this case?
Do I need to follow the same steps?
The text was updated successfully, but these errors were encountered: