Closed MDRafi08642 closed 3 months ago
I'm unable to help you at this point, please have in mind that creating an issue titled "Not working!!!" is very unprofessional, and does imply on others that this project is not up to date.
There are few issues:
You didn't share any output, connect to a serial monitor and then restart the board to see what it outputs.
Your board may not be compatible, I only found this entry "VCC-GND YD-ESP32-S3 (N16R8)", if that's your board and it's not working, well, revert to point 1.
PS: The output of boot.py is irrelevant, look for output of code.py
Good luck 🍀
@FLOCK4H Yeah that's the Same model.
And here's the serial output: (uart port COM5)
@FLOCK4H & here's the output using Putty: (usb port COM7)
I have pressed "any" key, Then ctrl+D.
Great! You have successfully debugged your issue.
Your ESP does not have a button named BTN, so you must modify source code of AtomDucky to reassign the button.
import board
dir(board)
Happy to see your progress, keep it up.
@FLOCK4H This is my board: (There are 2 buttons, boot & RST )
Here's the output using putty:
I have replaced "BTN" in with "GPIO12" buttons.py. (Now, working) But it's a pin, not a button.
It's okay, the button should not be necessary to run AtomDucky, so you're fine with the current setup.
Can I help you with anything else? Please close this issue if otherwise.
@FLOCK4H How to stop "BLE" attack On my board? & how to exit from "Rubber" mode On my board?
@FLOCK4H How to stop "BLE" attack On my board? & how to exit from "Rubber" mode On my board?
By pressing the button. Try to assign BOOT button in place of GPIO12, it may not work, as BOOT may be reserved by CircuitPy to do other stuff.
Read Usage section of README.md file please.
The initial issue was resolved, I'm closing this. Contact me privately for any further assistance.
@FLOCK4H I will try. But you can check issues on RPI pico W board. Thanks.
Model: ESP32-S3 N16R8
I have installed CircuitPython 9.0.5. Copied and pasted all files to the CircuitPython drive. Plugged and unplugged, but nothing happened. No access point was created or something.
Here is the content of the boot_out.txt file: