-
Notifications
You must be signed in to change notification settings - Fork 12
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
ESPlink v1.2 boards without firmware #5
Comments
Hi, Can you take a picture of how you wired it? |
No wiring other than a high quality USB C to C cable directly from laptop to ESPLink adapter.
Just to see device coming up as a wireless master and check out firmware
On 27 Aug 2024, at 03:09, wuxx ***@***.***> wrote:
Hi, Can you take a picture of how you wired it?
—
Reply to this email directly, view it on GitHub<#5 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAYT7GAZNRUCHQ2GFNDCDG3ZTPGVFAVCNFSM6AAAAABNEYQUBSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJRGM3TQMZQHA>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Do you want to read the firmware of ESPLink itself? |
Not specifically, possibly to make a backup.
Only tried the read flash when no UART console boot output was visible via Serial
On 27 Aug 2024, at 08:04, wuxx ***@***.***> wrote:
Do you want to read the firmware of ESPLink itself?
—
Reply to this email directly, view it on GitHub<#5 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAYT7GAZYVXOUSDDMD5SRSLZTQJFNAVCNFSM6AAAAABNEYQUBSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJRGY2DENRRHA>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
If you want to read the firmware of ESPLink itself, you need to use another ESPLink to read it through the 6 contacts on the back of TYPE-C |
OK, I am beginning to understand the config.
Let me explain my requirements.
1. Ensure all 3 devices have latest firmware installed
2. Connect wireless, using 2 ESPLink devices, to a local devboard using ESP-NOW
3. Connect wireless, using 2 ESPLink devices, to a remote device not yet sure how?
Can you please provide me details on the first 2 steps, since I believe the 3rd step might require some software development..
Thanks
On 24/08/27, 08:09, "wuxx" ***@***.******@***.***>> wrote:
If you want to read the firmware of ESPLink itself, you need to use another ESPLink to read it through the 6 contacts on the back of TYPE-C
—
Reply to this email directly, view it on GitHub<#5 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAYT7GE6CKR65HAIWZZ7KNLZTQJ2VAVCNFSM6AAAAABNEYQUBSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJRGY2TANRUHE>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
I have got the basic working, connecting to a target device, bidirectional UART comms working, flash via drag n drop UF2 working. I saw that the firmware is dated 2024 (it looks like) so should be newer than the version on the GitHub repo. As next step I need to get to the ESP-NOW configuration, to monitor and flash a device wirelessly. If you can provide some input here much appreciated. Please keep in mind, 3 devices, 2 on targets and 1 on the host. |
You are currently modifying the source code to complete the customization function, right? As far as I know, the default firmware does not support ESP-NOW |
1. I am currently not modifying any software since I do not have your source code.
2. Whether your ESPLink v1.2 default firmware support ESP-NOW I cannot say, does it?
On 24/08/28, 13:40, "wuxx" ***@***.******@***.***>> wrote:
You are currently modifying the source code to complete the customization function, right? As far as I know, the default firmware does not support ESP-NOW
—
Reply to this email directly, view it on GitHub<#5 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAYT7GHGWAQB7WTSCXJG4S3ZTWZKXAVCNFSM6AAAAABNEYQUBSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJVGA4DSMZTGM>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
the software source code locate here, I just modify some io config. |
The default firmware for the ESP32_S3_USG_BRIDGE devkit (upgraded version of yours?) is actually coming from this https://github.com/espressif/esp-dev-kits/tree/master/esp32-s3-usb-bridge/examples/usb_wireless_bridge repo. It does currently support ESP-NOW accordingly to the documentation, but the challenge I see is that the hardware is slightly different. The ideal would be if you could update your device firmware to be based on the repo linked above and then add the LWIP support for remote access. The problem I have currently is that the original ESP23_S3_USB_BRIDGE hardware (with the ESP-NOW capable firmware) is not available anywhere in the world, not via Amazon nor AliExpress or anywhere else. What are your thoughts? |
ESPLink is based on ESP32-S2. The ESP32-S2 chip itself also supports ESP-NOW, which may require some porting work. |
My thoughts would be that the best place to start is repo I linked above. I already includes JTAG, ESP-NOW (wireless Host and Target), support for 3 LEDs etc. All it requires to be added is support for IP STA (Client) at the target side. S2 vs S3, non problem both will do the job. This will create a killer product, we will take 10x for starters... |
Hi @wuxx Sorry to bother again but just checking on whether you have had chance to look at the suggested repo above and considered adding the IP STA client support? We would be happy to be a beta tester for you and commit to take 10x units if we can get the basic functionality mentioned. |
Hello, sorry, the original code was designed by Espressif and we have not modified it. You may need to research to meet your own needs. |
I have bought 3x ESPLink v1.2 boards from AliExpress. I have connected all 3 boards, one at a time, to my MacBook Pro and the results are exactly the same.
When trying to read the flash using 'esptool.py -p /dev/cu.usbmodemD4F98D72B5421 read_flash 0 all ESPLink.bin'
Any suggestion for getting these to work will be appreciated.
The text was updated successfully, but these errors were encountered: