Search found 71 matches
- Wed May 24, 2017 10:56 pm
- Forum: ESP-IDF
- Topic: RS-485 support
- Replies: 27
- Views: 57315
Re: RS-485 support
Same here. I need to implement J1708. No issues at all with the ESP8266, but the new driver seems to be a bit of a mess.
- Mon May 15, 2017 10:04 am
- Forum: Hardware
- Topic: can bus circuit
- Replies: 4
- Views: 10640
Re: can bus circuit
And PLEASE, if you are connecting to a vehicle, use a proper automotive transceiver instead of the MCP2551 piece of junk. TJA1042TK/3 would work fine and has the correct logic levels for the ESP32.
- Fri May 12, 2017 7:16 am
- Forum: Hardware
- Topic: About the CAN controller.
- Replies: 175
- Views: 308064
Re: About the CAN controller.
A note - unless you are only going to configure on a hard power-up (instead of after firmware OTA or other reset), you should add the following after the Pelican mode change [MODULE_CAN->CDR.B.CAN_M = 0x1;]:
MODULE_CAN->MOD.B.RM = 1;
Otherwise, the code cannot change the module configuration.
MODULE_CAN->MOD.B.RM = 1;
Otherwise, the code cannot change the module configuration.
Re: OTA issue
Good to know, thanks!
Re: OTA issue
In case anyone is following along, looks like this is the operative paragraph: App partitions have to be at offsets aligned to 0x10000 (64K). If you leave the offset field blank, the tool will automatically align the partition. If you specify an unaligned offset for an app partition, the tool will r...
Re: OTA issue
It would be amazing to get some sort of response here........... When I adjust the flash tool to flash both regions and then manually switch, I get the following: I (118603) setupgrade: OTA Partition: 3FFB9A68 E (118662) esp_image: Segment 1 has load address 0x3f400010, conflict with segment data at...
Re: OTA issue
Also, here is my partition table [2MB flash]:
# Name, Type, SubType, Offset, Size
nvs, data, nvs, 0x9000, 0x4000
otadata, data, ota, 0xd000, 0x2000
phy_init, data, phy, 0xf000, 0x1000
factory, app, factory, 0x10000, 0xF8000
ota_0, app, ota_0, 0x108000, 0xF8000
# Name, Type, SubType, Offset, Size
nvs, data, nvs, 0x9000, 0x4000
otadata, data, ota, 0xd000, 0x2000
phy_init, data, phy, 0xf000, 0x1000
factory, app, factory, 0x10000, 0xF8000
ota_0, app, ota_0, 0x108000, 0xF8000
Re: OTA issue
Just in case I wasn't reproducing the binary correctly, I tried to write the OTA section with the flash tool as well: python /c/ESP32/esp-idf/components/esptool_py/esptool/esptool.py --chip esp32 --port /COM4 --baud 2000000 --before default_reset --after hard_reset write_flash -z --flash_mode dio --...
Re: OTA issue
If I change the partition table to rename the OTA partition to #0, the above step succeeds, but it doesn't boot correctly: I (12) boot: ESP-IDF v2.0-rc1-725-g07b61d54-dirty 2nd stage bootloader I (12) boot: compile time 22:59:14 I (13) boot: Enabling RNG early entropy source... I (14) qio_mode: Enab...
Re: OTA issue
To follow up, it looks like the image is loading correctly, as esp_image_basic_verify attests: E (145783) upgrade: Image verify: 0, size: 570432 E (145784) upgrade: Find part: 3FFB99D8; 1 0 D000 2000 otadata 0 E (145785) upgrade: OTA part: 3FFB9A68; 0 11 108000 F8000 ota_1 0 E (145785) upgrade: Rewr...