Chorus32-ESP32LapTimer
Chorus32-ESP32LapTimer copied to clipboard
Compiling on Platformio?
The ESP32LapTimer.ino file says to check the readme but the information there is quite sparse :)
UPDATE: Here is how I did it.
- Pull Chorus32 from github
- Install Atom
- Install Platformio
- Import Arduino project in Platformio
- Specify the upload port in platformio.ini (eg.
upload_port = /dev/cu.Repleo-CP2102-0001
) - Start Platformio Terminal (shift+command+T)
- Run
pio run -e BOARD_OLD -t upload
- Hold boot button (important on my board!)
- Run
pio run -e BOARD_OLD -t uploadfs
- Hold boot button
- Connect to
Chorus32 LapTimer
wifi - Open http://192.168.4.1/
- You should now see the configuration page
Use BOARD_OLD
if you are using this wiring schema and BOARD_DEFAULT
if you're using the PCB v2.2 wiring schema.
I need as well more information - how to use platformio!
If you are running platformIO from the cli you can specify the env via the -e option, in case the port selection fails you can specify the port in the platformio.ini file for each environment See here: https://docs.platformio.org/en/latest/projectconf/section_env_upload.html#upload-port
pio run -e BOARD_OLD -t upload
Or use --upload-port on to specify in the run command as well :-) Hope I could help
I managed to build and upload the project using platformio using the steps described in the first post.
I haven't yet managed to specify the env target (BOARD_DEFAULT / BOARD_TTGO_LORA / BOARD_OLD) from the GUI. So need to use the CLI for now to build and upload.
This is how to compile Chorus32 with Bluetooth support...
- Uncomment
#define BluetoothEnabled
inESP32Laptimer.cpp
- Uncomment
#define USE_BLUETOOTH
inHardwareConfig.h
- Add
board_build.partitions = huge_app.csv
line toplatformio.ini
I won't recommend using Bluetooth. See #117
I'm sure one day bluetooth will be stable and this information might become useful :)
Also wifi is broken on app on Android 10 so bluetooth might be the only alternative for some.
But as of now, if you are using Bluetooth, the timer might crash any time, so I'd deem this unusable in the current state.
As for the Android problem: I should have a working fix by tommorrow
@Smeat Thanks for pointing that out. And looking forward to beta testing the android version :)
do we still need to change to BOARD_OLD in HardwareConfig.h?
Depends on which hardware your are using:
Use
BOARD_OLD
if you are using this wiring schema andBOARD_DEFAULT
if you're using the PCB v2.2 wiring schema.