Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chatgpt_demo stuck at Steps screen even after restart and CONFIG.ini updated (AEGHB-699) #153

Closed
vinny-888 opened this issue Jun 19, 2024 · 4 comments

Comments

@vinny-888
Copy link

I installed the chatgpt_demo from here (https://espressif.github.io/esp-launchpad/?flashConfigURL=https://espressif.github.io/esp-box/launchpad.toml) and everything worked perfectly

I checked out the latest code and compiled and was able to flash the code from the chatgpt_demo example onto my ESP32_S3_BOX_3

When the app starts up I get the "Steps" screen and even after I set the CONFIG.ini settings and click restart, I end up back at the Steps screen and cannot get passed it.

Not sure if there is a known but or how I might be able to bypass this as I have set these settings also in the sdkconfig

CONFIG_ESP_WIFI_SSID="xxx"
CONFIG_ESP_WIFI_PASSWORD="xxx"
CONFIG_OPENAI_API_KEY="sk-xxx"
CONFIG_OPENAI_URL="https://api.openai.com/v1/"

Any help or tips on how to bypass this screen would be great

@github-actions github-actions bot changed the title chatgpt_demo stuck at Steps screen even after restart and CONFIG.ini updated chatgpt_demo stuck at Steps screen even after restart and CONFIG.ini updated (AEGHB-699) Jun 19, 2024
@Horion0415
Copy link

You can try erasing the flash and then flashing the chatgpt_demo from the launchpad. The erase command is: idf.py -p /dev/ttyACM0 erase-flash. Alternatively, you can try compiling the project yourself and flashing it to see if the same issue occurs.

@vinny-888
Copy link
Author

Alternatively, you can try compiling the project yourself and flashing it to see if the same issue occurs.

Yes this only happens when building from source and flashing myself

When I load it from the launchpad it works as expected

@Horion0415
Copy link

Did you follow the compilation requirements in the README for the build? The compilation process for this example is different from other examples.

@vinny-888
Copy link
Author

Ah I missed the second build step so I must have just built the factory_nvs and not the actual app.

Once I built the app in the parent dir it runs as expected now.

Thanks for the tip not sure I would have caught I missed that. Eyes just saw the same commands and missed the folder change

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants