Skip to content

Commit

Permalink
Merge pull request #26 from UncleGrumpy/announce_0.6.9b1
Browse files Browse the repository at this point in the history
Fix bad descripion of `esp32_devmode` in release post
  • Loading branch information
fadushin authored Mar 1, 2024
2 parents d28580c + 07c5714 commit cc8be03
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion _posts/2024-02-29-Release_v0.6.0-beta.1.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ excerpt_separator: <!--more-->
We are pleased to announce that our pre-release of v0.6.0 is now in beta!

>Wait! What happened to the v0.6.0-beta.0 release?
>Our all volunteer QA team (thank you @petermm) discovered a problem with the ESP32S3 builds that prevented the default `esp32init.beam` from working properly. This is the default network application that will create a wireless AP, and allow you to upload an application to an ESP32 that has been flashed with the AtomVM image, but does not have a user application flashed yet. We have determined the cause of the problem, but it has not been fixed in this release. ESP32S3 users will need to flash an application over UART, and a crash-boot-loop is expected if the device is started without an application on the application partition.
>Our all volunteer QA team (thank you @petermm) discovered a problem with the ESP32S3 builds that caused starting `esp32init.beam` to crash the VM. This is the default network application that will create a wireless AP on an ESP32 that has been flashed with the AtomVM image, but does not have a user application flashed yet. Once connected to the "AtomVM-ESP32" network that is created you can access an alisp console at 192.168.4.1 on port 2323, or connect to http port 8080 to change the network to station mode and connect to a wifi network, where the arepl console will be available on port 2323 on the devices acquired IP address. We have determined the cause of the problem, but it has not been fixed in this release.
In this release [SPI](https://www.atomvm.net/doc/v0.6.0-beta.1/apidocs/erlang/eavmlib/spi.html), [I2C](https://www.atomvm.net/doc/v0.6.0-beta.1/apidocs/erlang/eavmlib/i2c.html), and [UART](https://www.atomvm.net/doc/v0.6.0-beta.1/apidocs/erlang/eavmlib/uart.html) peripheral configurations have been changed, for details consult the documentation for these modules in the [`eavmlib` documentation](https://www.atomvm.net/doc/v0.6.0-beta.1/apidocs/erlang/eavmlib/README.html). There is now an ESP32 API for allowing coexistence of native and Erlang I2C drivers, for example, allowing the use of the native [`atomvm_ssd1306` Display driver](https://github.com/atomvm/atomvm_ssd1306), with a pure erlang driver for the [SHT3x temperature sensor](https://github.com/atomvm/atomvm_examples/tree/master/erlang/i2c_example). GPIO interrupt (currently only supported on ESP32 and STM32 platforms) messages can now be sent to a designated receiver using `gpio:set_int/4`. Support for `lists:split/2` has also been added. ESP32 platform now supports retrieving the device's e-fuse MAC address with `esp:get_default_mac/0`.

Expand Down

0 comments on commit cc8be03

Please sign in to comment.