You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Arduino IDE 2.3.3 & arduino-cli 1.0.0-4c.1 Commit: ba19a2d3
Operating System
Ubuntu 22.04.4 LTS
Auto Flash Mode
Disable
Erase All Flash Memory (16MB)
Disable
Standard Lib
Arduino_STD_PRINTF
Upload Speed
2000000
Description
I am having issues using the ameba-OTA-UI to properly run OTA when linked to the example OTA project in the following dev release 4.0.8-build20241003.
Frist I changed the ip address in the ota_drv.c file shown below:
That made me able to get my device to show up in the UI as shown below:
However, i can't seem to get the OTA to trigger using the UI. to further clarify the following is the response on the device side:
[http_update_ota] Download new firmware begin, total size : 5447680
[http_update_ota] Current firmware index is 1
..
[ota_flash_NOR] target_fw_addr=0x520000, target_fw_len=0x10000
[http_update_ota] ota flash failed
On the UI side the folloing request seems to error out:
for further context the connectedclients request seems to be working properly:
But the start_ota request seems to have an issue in getting a proper response:
Any help would be appreciated. I plan to take a deeper look at the OTA drivers, but was wondering if there was something obvious i was missing before doing so.
Sketch
#include"ota_thread.h"
#include"WiFi.h"char ssid[] = "Network_SSID"; // your network SSID (name)char pass[] = "Password"; // your network passwordint status = WL_IDLE_STATUS;
voidsetup()
{
Serial.begin(115200);
// Connection to internetwhile (status != WL_CONNECTED) {
Serial.print("Attempting to connect to WPA SSID: ");
Serial.println(ssid);
status = WiFi.begin(ssid, pass);
delay(2000);
}
// Set up the threadsstart_OTA_threads();
}
voidloop()
{
// Empty or add non-blocking code here
}
Error/Debug Message
See Description (No Compile or upload error).
Reproduce remarks
No response
I have checked online documentation, FAQ, GitHub Wiki and existing/closed issues.
I confirm I have checked online documentation, FAQ, GitHub Wiki and existing/closed issues.
The text was updated successfully, but these errors were encountered:
hi @TeaBear5 , I think you have missed out the following steps in creating the OTA firmware image.
Set NN Model Load From SD Card. “Tools” -> “NN Model Load From” -> “SD Card”
Enable the OTA mode. “Tools” -> “OTA Mode” -> “Enable”
Compile the code again using Arduino IDE, you will then find the ota.bin file in the /home/username/.arduino15/packages/Realtek/tools/ameba_d_tools/x.x.x/ folder
This is the .bin file to be uploaded to your UI server for OTA trigger.
Boards
AMB82-MINI
External Hardware
USB Connection to PC
Hardware Configuration
None
Version
latest dev (checkout manually)
IDE Name
Arduino IDE 2.3.3 & arduino-cli 1.0.0-4c.1 Commit: ba19a2d3
Operating System
Ubuntu 22.04.4 LTS
Auto Flash Mode
Disable
Erase All Flash Memory (16MB)
Disable
Standard Lib
Arduino_STD_PRINTF
Upload Speed
2000000
Description
I am having issues using the ameba-OTA-UI to properly run OTA when linked to the example OTA project in the following dev release 4.0.8-build20241003.
Frist I changed the ip address in the ota_drv.c file shown below:
That made me able to get my device to show up in the UI as shown below:
However, i can't seem to get the OTA to trigger using the UI. to further clarify the following is the response on the device side:
On the UI side the folloing request seems to error out:
for further context the connectedclients request seems to be working properly:
But the start_ota request seems to have an issue in getting a proper response:
Any help would be appreciated. I plan to take a deeper look at the OTA drivers, but was wondering if there was something obvious i was missing before doing so.
Sketch
Error/Debug Message
Reproduce remarks
No response
I have checked online documentation, FAQ, GitHub Wiki and existing/closed issues.
The text was updated successfully, but these errors were encountered: