Avatar for SimonGAndrews


Member since Aug 2021 • Last active Jun 2024
  • 6 conversations

Retired Solution Architect (Xerox - Imaging Services)
Working on implementing Xstate
on Microcontrollers for improving Service Delivery

Most recent activity

  • in General
    Avatar for SimonGAndrews

    Hi , thanks @Gordon , I think I can see your structure and general approach: flash/run tests in node on a host, use a board config that specifies test paramaters the relevant tests, structure test scripts in the file system on the host, using a standard test execute method from node around the Espruino CLI tool. All makes good sense.
    And your thoughts or collecting various stats, with simple analysis eg comparison of test runs over time/ builds makes sense too. Your approach would allow small test result stats files (eg JSON) to be stored on the host over time, in a boards structure, and analysed with a tool there. A configuration of the relevant stat and measurement function for a board could work.
    Lots to think about. But I get your framework and the idea of structuring tests this way now to evolve the whole concept.

  • in General
    Avatar for SimonGAndrews

    I note there are thoughts on bangle testing bangle apps https://forum.espruino.com/conversations­/395324/
    But not quite the same problem/solution

  • in General
    Avatar for SimonGAndrews

    Hi , in the context of testing out a new build of Espruino such as the ESP c3 and how to approach this.

    1) I stumbled across the Espruino/test directory in github , and testing with ./Espruino --test,
    But it looks like this is for running in a linux build of Espruino only. Is that correct ??

    2) is there an approach to structuring tests for a new build? I suppose:

    • it would be useful to have tests that can be repeated, particularly incases where the build may well go thru further iterations (eg IDF 4.x , idf5.x).
    • tests will be exercising hardware and peripherals, so will need to have board connection, i2c devices , network etc.
      • maybe at the at least structuring some simple JS scripts with documented and simple connection setup that can be repeated for a family of devices.

    Any thoughts on this. I May make a stab at it for the ESP C3 build .

  • in ESP32
    Avatar for SimonGAndrews

    Thanks @MaBe and others got both the mini and OLIMEX c3-Devkit (link above) flashed today. Both working in the WebIDE , ESP32.reboot() and .getstate() working, program upload from IDE is good. Connected to WIFI ok. Looking very good. Im off for a couple of weeks but will test properly on return. Will look the i2C and IO first. Great job folks.

  • in ESP32
    Avatar for SimonGAndrews

    Me also, I cant find a guide that uses sudo, but was in my notes, an error on my part.

    And now without Sudo, in a clean git clone of Espruino, without any changes to the make files:

    source ./scripts/provision.sh ESP32C3_IDF4
    BOARD=ESP32C3_IDF4 RELEASE=1 make flash

    Is building to completion (i will sort flashing). :)

    Thanks again @fanoush. I appreciate your help.

  • in ESP32
    Avatar for SimonGAndrews

    Thanks @fanoush , i get your point, Ill blast the Espruino clone and try again without the sudo.

  • in ESP32
    Avatar for SimonGAndrews

    Hi, im slowly getting to a position to build Espruino for the C3. Ive put Ubuntu v24.4 on an old dell 3050 for this. Im not experienced with Ubuntu just to say.

    I think I have the same issue as @Jean-Philippe_Rey when running '>sudo BOARD=ESP32C3_IDF4 RELEASE=1' with the error 'idf.py not found'.

    This was after running the provision script and checking that idf.py did run in Espruino and Espruino/bin from the terminal prompt.

    I found putting the directory names in front of idf.py in the file /Espruino/make/targets/ESP32_IDF4.make fixed this.

    When running the Espruino build line, Im getting past theis idf.py not found error now and hitting another error 'packaging cannot be imported' . So something missing in my ubuntu, I suppose. But idf.py will build a bin on its own in the idf/examples??
    Ill push on. Ive only got a little time over the next couple weeks.

  • in ESP32
    Avatar for SimonGAndrews

    Great news to see these developments to catch up the esp32 builds to newer IDF versions and to move away from the existing build to cmake method. I’m following closely and will try to help with testing.
    This looks a usefull esp-c3 board (2 in the post) that supports the ESP-PROG-C which may help with debugging. https://thepihut.com/products/olimex-esp­32-c3-devkit-lipo-risc-v-development-boa­rd

    @rgomezwap glad to see your work getting closer to Main stream and thanks to @Gordon particularly and @MaBe for running with this.

  • in ESP32
    Avatar for SimonGAndrews

    Further to above, after a few builds of Espruino ( with make clean && BOARD=ESP32 make) having added some console prints to /targets/esp32/jshardwarePulse.c I am pretty sure that this code is not executed on a digitalPulse function call.

    With similiar tests it does look like the function is built in src/jswrap_io.c and the function jswrap_io_digitalPulse() is used to execute the call..

    Looking though this code I can not see any special treatment for the ESP32.

    My C skills are at the 'cut and paste level', so It will take me allot more time to try to figure out the issue (pulse period not varying) in that code and the risk is this method hasnever beentestd and just does not work on the ESP32.

    Im going to raise an issue just in case, but I dont think I can take this much further.

    Please bring on a supported Espruino WIFI option (with lower overhead than a an Espruino Pico with ESP83266 he says with tears in his eyes. :)