Run tests on feature/smp

[bettio]

Following manual tests should be executed on real hardware using feature/smp and latest esp-idf version. In case of failure, it must be compared with master branch and an issue should be reported.

Please, write down here in the comments if anyone is willing to take care of any of the following tests.

ESP32 sockets and networking:

• [x] receive UDP packet in active mode
• [x] receive TCP packet in active mode
• [x] receive UDP packet in passive mode
• [x] receive TCP packet in passive mode
• [x] receive in binary mode
• [x] receive in list mode
• [x] send in binary mode
• [x] send in list mode
• [x] connect to wifi (significant events are received)

ESP32 peripherals:

• [x] GPIO blink led (+ check jitter)
• [x] GPIO interrupt
• [x] GPIO digital read
• [x] I2C write_bytes
• [x] I2C read_bytes
• [x] SPI read_at
• [x] SPI write_at
• [x] SPI write (transaction)
• [x] SPI write_read
• [x] UART read
• [x] UART write
• [x] LEDC functions

ESP32 misc:

• [x] native display driver can be ported and works (with good performances)
• [x] sx127x.erl example
• [x] morse_server.erl example
• [x] udp_server_blink.erl example
• [x] tcp_server_blink.erl example
• [x] ledc_example.erl example
• [x] tcp_client_esp32.erl example

STM32 peripherals:

• [x] GPIO blink led (+ check jitter)

~- [ ] GPIO interrupt~ ~- [ ] GPIO digital read~

[bettio]

Trying to test uart:read(UART) but it doesn't work. See also #565.

[UncleGrumpy]

STM32 does not have a digital read yet, or interrupt support, only digital write (#571). Digital write is broken, but can be fixed with the merge of #447. I thought I opened an issue at the same time, but apparently for got so that is issue #570.

[UncleGrumpy]

ESP32 sockets and networking:

✅ receive TCP packet in active mode ❌ TCP receive in binary mode ✅ TCP receive in list mode ✅ TCP send in binary mode ✅ TCP send in list mode

More results soon...

[UncleGrumpy]

My mistake, binary receive in esp32 causes a Guru meditation error...

❌ TCP receive in binary mode

See Issue #582

[UncleGrumpy]

✅ TCP receive in binary mode.

582 was a red herring...

[UncleGrumpy]

The blink.avm from atomvm/AtomVM/examples/erlang/esp32/blink.erl, and both the AtomVM and atomvm_examples versions of the morse_sever suffer from the same bug (see Issue #584) but are functional with modifications.

[UncleGrumpy]

✅ GPIO blink led ✅ GPIO interrupt ✅ GPIO digital read

as far as jitter goes there is some steady incremental time loss in the blink example, not sure it it warrants an issue or not. Here is an attached logic analyzer scan taken with 12Mhz sample rate: blink_100ms.sr.tar.gz

[bettio]

as far as jitter goes there is some steady incremental time loss in the blink example, not sure it it warrants an issue or not. Here is an attached logic analyzer scan taken with 12Mhz sample rate: blink_100ms.sr.tar.gz

Can you attach the source for reference too?

[UncleGrumpy]

Here is the Erlang source for the test I used to acquire the above logic traces. blink.erl.tar.gz

[UncleGrumpy]

More network test results:

✅ receive TCP packet in passive mode

✅ receive UDP packet in active mode ✅ receive UDP packet in passive mode ✅ UDP receive in binary mode ✅ UDP receive in list mode ✅ UDP send in binary mode ✅ UDP send in list mode

✅ test morse_server.erl

[UncleGrumpy]

The blink.avm from atomvm/AtomVM/examples/erlang/esp32/blink.erl, and both the AtomVM and atomvm_examples versions of the morse_sever suffer from the same bug (see Issue #584) but are functional with modifications.

I have updated #584, it is not specific to feature/smp... the regression happened in master sometime in the last 12 months.

[UncleGrumpy]

✅ STM32 GPIO blink led (+ check jitter).

Blink works on stm32, and is not affected by issue #584. The attached logic analyzer trace shows a very consistent time lag similar to the esp32. Is it approximately 3ms lost for each 100ms. Also attached is the Erlang source used for the test. stm32_blink_100ms.sr.tar.gz blinky_stm32.tar.gz

[UncleGrumpy]

✅ ledc_example.erl example

❌ udp_server_blink.erl example ❌ tcp_server_blink.erl example ❌ tcp_client_esp32.erl example

See issue #592

[UncleGrumpy]

Both the udp_server_blink and tcp_server_blink will work if modified to use atoms rather than numeric values (0 or 1). See #584

tcp_client_esp32 sill suffers from #592.

[UncleGrumpy]

✅ tcp_client_esp32.erl example. Fixed in master #595, so that will be fine after merging.

[UncleGrumpy]

When #604 is merged the following examples work correctly: ✅ tcp_server_blink.erl ✅ udp_server_blink.erl

[UncleGrumpy]

✅ UART write