- 0
ESP-Board visible in the firmware flasher-tool, but not VSCode - what to do!?
-
Recently Browsing 0 members
- No registered users viewing this page.
-
Posts
-
By TsarNikky · Posted
How many other companies will follow Ford's lead? Or, have they already gotten lazy and become enslaved to AI--and now can't figure out how to get out of that mess. -
By TsarNikky · Posted
Why would any self-respecting intelligent person follow any recommendation by Donald's GOP administration? With almost two years of fabrications, deceit, and blatantly illegal behavior, why believe them now? They had best be gone after the November 2026 election, so we'll wait and see. -
By Copernic · Posted
AltSendme 0.4.1 by Razvan Serea AltSendme is a minimal, cross-platform application designed for fast, secure, and private peer-to-peer file transfers. It allows users to send files or entire directories directly between devices without relying on cloud servers, accounts, or any personal information. Everything is encrypted end-to-end using modern protocols like QUIC and TLS 1.3, ensuring both strong security and low-latency performance. Transfers are verified with BLAKE3 for data integrity, and interrupted downloads automatically resume, making the experience reliable even on unstable connections. You can transfer anything—images, videos, documents, and more. Integrity checks are performed on both ends, so your files are automatically verified for correctness during both sending and receiving. AltSendme works seamlessly across local networks or long-distance links, capable of saturating multi-gigabit connections for extremely fast delivery. With built-in NAT traversal and encrypted relay fallback, it connects devices almost anywhere. The app integrates with the Sendme CLI and will soon support mobile and web platforms. Fully free and open-source, AltSendme offers a lightweight, privacy-first alternative to traditional cloud-based services, removing size limits, upload costs, and unnecessary data exposure. AltSendme 0.4.1 changelog: Release Highlights Self-hosted relays: Run your own iroh relay so transfers don't rely on public infrastructure. Includes a full deployment template in deploy/relay/ with Docker Compose for a VPS and configuration examples for production use. Fly.io support: One-click deploy template for Fly.io, including a quick-start config (fly.dev.toml) for testing without a custom domain, plus production setup with Let's Encrypt and your own hostname. Relay settings UI: New Settings → Network panel to choose how AltSendme connects: automatic public relays, custom self-hosted URLs (with optional auth token), or disabled. Test connections, verify latency, and see live relay status in the footer. Disable relays: Turn off relay servers entirely when you only need same-network transfers (e.g. LAN). Direct connections only. No relay hop required when devices can reach each other. Android graduates from beta: Android is now part of the regular release cycle alongside desktop. APKs ship with each version (universal, arm64, and armv7). Other improvements Private relay access control via shared auth token Relay fallback notifications when a custom relay is unreachable Broadcast mode toggle in sharing settings Android release build fixes (split-per-ABI APKs, universal APK preservation) UI polish: mobile safe-area insets, dropzone layout, transfer progress animation Bug fixes for minification-related serialization issues and system tray icon loading What's Changed feat(relay): add relay status functionality and settings UI (a120cdf) feat(relay): implement custom relay server configuration and verification (51276c7) feat(relay): add configuration for private relay access and enhance observability features (48fbabf) feat(relay): enhance relay URL validation, display connection status (d4fffa0) feat(relay): add RelayChangeGuard component and enhance relay-related translations (16ba514) feat(broadcast): add toggle setting for broadcast mode in sharing UI (ca6d977) fix(relay): correct QUIC discovery port, pin image, templatize fly.dev (52a2ba5) fix: More broken serialization due to minification (67491a9) fix(android): preserve true universal APK across per-ABI builds (e9f256f) fix(ui): conditional safe-area insets padding on mobile (1182f0e) refactor(transfer): CircularRing component animation fix (944572b) chore(android): drop x86 and x86_64 release APKs, keep universal+arm64+armv7 (34ada0b) Download: AltSendme 0.4.1 | ARM64 | ~9.0 MB (Open Source) Download: AltSendme for MacOS | Android Links: AltSendme Home Page | GitHub | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware -
By zikalify · Posted
You are mostly right about the ephemeral nature of it. As I mention in the article, if you dont add a second device or take a backup of your account before uninstalling it, then yes you will lose access to your account. That said, in terms of actual user experience when you sync multiple devices your message history carries across and there's also a Saved Messages chat like there is on Telegram to send messages and attachments between your installs. But yh, what you point out are correct and its not trying to emulate Messenger or Telegram. -
By zikalify · Posted
OK so SearXNG is a meta search engine that you can install locally or use via a public instance. It scrapes other search engines which you choose and then sorts the results. Not as complicated as multiple relays
-
-
Recent Achievements
-
flexorcist earned a badge
Week One Done
-
Woland13 earned a badge
One Month Later
-
Woland13 earned a badge
Week One Done
-
bernmeister earned a badge
One Year In
-
Scoobystu earned a badge
Week One Done
-
-
Popular Contributors
-
Tell a friend
Question
tarifa
hello dear Community,
the topic: ESP-Board visible in the firmware flasher-tool, but not VSCode - what to do!?
ESP-Board visible in firmware flasher-tool, but not VSCode I use MicroPython to program microcontrollers, especially the ESP32/ESP8266 types. These two microcontrollers are pretty good compatible with MicroPython and it is easy to integrate sensors and actors programming using this language
i run vscode on windows - and on Linux. on Windows i am facing several issues: i am happy that i am using MicroPython extension, and have successfully flashed the MicroPython firmware (Operating System) to the ESP8266 target device.
Note: The Flashing was pretty easy: it worked as a breeze i was using the NodeMCU flasher tool through a serial COM port of the Notebook.
i have installed / enabled the following plugins/extensions so far:
- C++
- Native Debug
- Code Outline or AL Outline (to display and navigate properties)
- Additionally - ASM Code Lens extension - for ULP ASM
- PyMakr https://blog.jetbrains.com/pycharm/2018/01/micropython-plugin-for-pycharm/
and https://github.com/vlasovskikh/intellij-micropython
a great guide also visible here https://lemariva.com/blog/2018/12/micropython-visual-studio-code-as-ide
I did the following steps: After creating a new project by selecting the project folder.
Then i want to look for the ports to connect.
but the system gives back that "auto detection of COM ports isn't available for Windows
version of Visual Studio Code. I'm prompted to manually enter the COM port
I've tried tp connect the target MicroPython device (a ESP 8266) to, and VSC gives back the following report:
Port not exist, please connect device and try again!what did i have tried:
- I've tried all available 3 USB ports,
- reinstalled the driver software,
- rebooted the computer,
- power cycled the target device and
- made sure the target device is in program flash mode (that i did to allow application to be written to it) each time I try to connect VSC to it!
what do you suggest me to do!?
many thanks for every idea sharing and help
Link to comment
https://www.neowin.net/forum/topic/1387547-esp-board-visible-in-the-firmware-flasher-tool-but-not-vscode-what-to-do/Share on other sites
1 answer to this question
Recommended Posts