Search results for:

I suspect
1) that you do not have the correct drivers installed on the PC for the UART to USB connection you are using. or
2) maybe not using the correct com port.

Regarding (1) The ESP UART to USB connection will need to use a chip (in the cable or on the board) that needs the correct driver. Eg FTDI chip neeeds drivers from here https://ftdichip.com/drivers/

I you need more help, please explain , How are you making the connection between the board and the PC. Share a picture of the CABLE between the board and the PC which shows how the cable is connectedto the ESP32 board and describe ESP32 board you are using.

regarding (2) it looks like from your picture the WebIDE thinks it is connected to a com port. If the Baud rate is correct then the IDE is still not receiving ESPRUINO response on the com port. Are you sure Com8 is the correct COM port? Maybe something else is on Com8 (not esp32). Use device manager to see what com ports are active. But if the drivers are not corrrect then the com port may not be assigned (visible in device manager) or it may be assigned and show an error in device manager.

Good luck,

Thanks @MaBe , your phases make sense and I see your good work on #2370;
Its not easy, I am sure, very tricky stuff.

Any help understanding on exacly which scripts are run to make the the travis and release builds would be appreciated. I suppose they are some of the scripts in EspruinoBuildTools but which ones are used? Its background infor for me to understand when the idf build output (stored in the deploy zips) is being updated in these production builds. For example they could run from EspruinoBuildTools: build-idf.sh then build-tgz .sh or maybe just build-tgz.

Hello,
Could someone help me please understand exactly what scripts are executed to build the Espruino ESp32 bins found at https://www.espruino.com/binaries/travis? Also is that the same scripts building released versio bins at //www.espruino.com/binaries/.
Are the scripts visible somewhere??

Im still trying to understand better the ESP32 build. The reason is:
Im having some success building it in windows / VScode with the ESP-IDF tools (V3.3.6) using cmake - actually flashed a working V18 version today.
Im going to have a go at modifying this to try and build in ESP-IDF (V4.x) to contribute in that direction . (tricky stuff for me .. no one hold breath please).

Hello,
I was getting similiar issues.
There was a fix deployed in v 2v17.74 on the May 5 which may fix this. You can find the bins in the travis/master directory. http://www.espruino.com/binaries/travis/master/
Maybe try again with the new version.

Hi,
Find attached a visual of the ESP32 build script process. It shows the build scripts and how they interact with the build files you get from a clone of
git clone --recursive https://github.com/espruino/EspruinoBuildTools.git .

I did it to try and understand the process myself , sharing in case usefull to anyone. As alway im open to any corrections or feedback. If PDF, Visio source or JPG is more usefull. Let me know.

Hello,
I was getting similiar issues.
There was a fix deployed in v 2v17.74 on the May 5 which may fix this. You can find the bins in the same travis/master directory you referecne above. Maybe try again with the new version.

Ah … funny indeed … I missed the link. Well done on the tools. Hopefully these will inspire a few to get involved in a port of espruino. I’m still up for supporting but can’t manage it on my own. I’ll be trying the out the probe soon. Cheers

News of simpler solution to install tool chain for developing for Raspberry Pi Pico using C or C++ on Windows in VS Code. https://www.raspberrypi.com/news/raspberry-pi-pico-windows-installer/

Also new debug probe for £12. https://www.raspberrypi.com/news/raspberry-pi-debug-probe-a-plug-and-play-debug-kit-for-12/

Talking hobbies over Belgian beer sounds brilliant.
Sorry not to make it his year. Enjoy.

Looks like Raspberry Pi Pico W (wireless) is also to get Bluetooth LE support very soon according to this .
On another thread @JumJum wrote last year on his efforts on a port to the Pi Pico W but has gone quiet now.

I’m very intrigued. But also recognise the challenge to Espruino commercial model.
I had a look at how to build on all the above, but can’t quite see the way through.

Hi,
Ive got a version of this change that im testing. Ive set out an issue https://github.com/espruino/EspruinoTools/issues/154
to track this as a change. See the issue for more detail and link to my fork.

Ok, Ill have a go. Thanks

Thanks @fanoush , that's a great start.

yes please for a patreon symbol, regards Simon

Hi,
Is there an existing way to colour text being displayed in the Web IDE Terminal window.
Specifically for colouring the text from the execution of console.log('string') in espruino.

It seems a common method would be to prefix the string with an ANSI escape sequence such as
Red: \u001b[31m. or green
Green: \u001b[32m
This works in node in vscode.

Ive tried this in Espruino WebIDE

console.log (" \u001b[31m HelloWorld ");

and it looks like the the escape sequence is being trapped , because not all of it is printed.

Ive had a poke around the WebIDE code on github but I cant find the code that handles the terminal window. I can see that there is colour styling of the code editor window.

My use case is im having a quick look at the feasability of a simple jest style unit testing tool and would like to colour the output to the console. Which looks good so far. (colour is a bit of a nice to have I would agree)

Any cluse on an approach to implement the coloured output text appreciated. And a high level of how the terminal window is driven ??. Is there is some escape sequence to HTML going on somehwere ??

Thanks in advance, Simon

@JumJum , i hope you are well.
Do think you will be sharing anything further on this ?
No pressure just interested in seeing this happen one day, and supportig if needed.

I would be interested to help setup USB (both device (HID etc) as existing Espruino and new host functionality). Testing the mapping of console to serial etc as I go.

I have got your port building using VSCode on Windows. Espruino is firing up in the Espruino IDE. Interactive is executing but save to flash and execute is not. Im going to try and setup a Debug test rig (with RP Pico W) as per https://community.element14.com/products/raspberry-pi/b/blog/posts/debugging-the-raspberry-pi-pico-on-windows-10

Please can you share any updates when you can.

Great news, I would like to help.

@JumJum thanks for sharing this. And well done.

Move to github discussions sounds positive to me. Improving searching would be a big plus. Lower admin also a plus.

so Ive had my implementation of Xstate in Espruino on hold while working on getting USB Host working on Pico (both essential to my project) . But the status of Xstate in Espruino work is well beyond proof of concept and is a point of testing nested states , which are one of the most basic yet usefull extensions of statecharts over simple finite state machines.

But in parallel the Xstate world is moving on leaps and bounds.
https://stately.ai/blog/stately-editor-public-beta
Now the capability is there to design with drag and drop , inside visual studio, a state chart representation of a finite state engine and generate the javascript code and object definition of the state engine.
So this means with a small javascript framework in Espruino we would be able to change the logic of our microcontroller in a standard , visual representation, readily transferrible from one Espruino Hardware environment to another. Theres a great vision here. (just got to get USB host working !!)

check out Xstate when you can and imagine it working in Espruino.

will update ASAP

A little wire wrapping going on in the mean time. :)

P.s any advice always appreciated.

Quick status ... still putting in lots of hours on this. Steep learning curve for me. Achieved so far,

• building Espruino for pico on Ubuntu and getting vars for build
  
• building Espruino in Stmcube ide with hacked make file.
  
• Wired up pico with swd via a Nucleo SWD and so able to run debug via stmcube ide on Espruino interpreter, with power and active console via serial on pico, so can trace thru existing interpreter functionality eg serial.inject. (See pics attached)
  
• Started custom lib in Espruino Usbhost , with jswrap_usbhost
  
• got standalone stmcubef4 usb host library running with a simple main on discovery board. Can see init and receive data callbacks that need to be implemented in Espruino idle loop via wrapper.
  
• Currently copying over usbhost library components from stmcubef4 and trying to build Espruino with them included, issues are newer versions of common files down the usb stack that are shared With existing Espruino usb client stack. Trying to understand and work the overlap. Don’t want to give up on building with both host and client stacks in place.
  
• Initial dev target is ‘just’ disable usb client, init usbhost, and print received data to console.
  
• I will be seeking advice , in due course, on plumbing in usbhost cdc get data into an usbhost.on(‘data’, callback) via the wrapper functionality. Looks like serial.inject has some clues.