ya3

Forum Replies Created

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • in reply to: ESP32 ULP programming #32364
    ya3
    Participant

    Yup it appears to be esp-idf issue.
    Digging deeper into it, looks like the 4.4 release does not have support for the ULP of the S3 🙁

    in reply to: Esp-idf 4.4/ ESP32-S3 #32346
    ya3
    Participant

    Gotcha, thanks!

    Final question, I am playing around with the Automatic Include Path Discovery feature. I see that it adds entries to cmakelists as relative paths. I’d like to change some of these to use an absolute path and I was wondering if there is some mechanism that propogates the visualgdb project variables over into cmake. For example, I’d like to path something in cmakelists by using $(ToolchainDir) variable. Is that possible currently?

     

    Thanks

    in reply to: Esp-idf 4.4/ ESP32-S3 #32340
    ya3
    Participant

    I still do not understand where that IDF_TARGET comes from as what is printed in the build log does not match what is in the XML file. Nowhere in the xml is the “esp32s3-beta2” string found. Comparing that XML between v4.3.2 and v4.4 there is no difference there.
    Guess that does not matter much now that r8 is out with support for 4.4

     

    As far as the jtag thing, I just tried it with the official esp32 openocd binary (v0.11.0-esp32-20211220) under ubuntu 2.04 and it worked. I ended up playing around with available drivers and eventually found that WinUSB and libusb-win32 were not working but after trying with libusbK, it ended up finally working from initial inspection.

     

    Thanks

    in reply to: Esp-idf 4.4/ ESP32-S3 #32333
    ya3
    Participant

    Not really sure what is meant by the first part.
    That BSP.xml file does not change between idf 4.3.2 and 4.4 but the command to program the esp does. The command goes from     “–chip esp32s3-beta2”   to “–chip esp32s3” when switching between idfs. Not really sure what determines that –chip parameter when trying to flash the esp.

     

    I went ahead and tried v4.4 and it seems to work on a hello world. What does not seem to work is the s3 built in USB-JTAG. After switching the driver over to libusb-WinUSB, attempting to conenct to the s3 over the usb jtag just results in this (repeated multiple times until a timeout):

    Warn : Transport “jtag” was already selected
    VisualGDB_OpenOCD_Ready
    Info : Listening on port 6666 for tcl connections
    Info : Listening on port 59091 for telnet connections
    Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
    Info : esp_usb_jtag: Device found. Base speed 40000KHz, div range 1 to 255
    Info : clock speed 3076 kHz
    Error: libusb_bulk_write error: LIBUSB_ERROR_NOT_FOUND
    Error: libusb_open() failed with LIBUSB_ERROR_ACCESS
    Error: libusb_open() failed with LIBUSB_ERROR_ACCESS
    Error: libusb_open() failed with LIBUSB_ERROR_ACCESS
    Error: libusb_open() failed with LIBUSB_ERROR_ACCESS
    Error: libusb_open() failed with LIBUSB_ERROR_ACCESS
    Error: libusb_open() failed with LIBUSB_ERROR_ACCESS
    Error: esp_usb_jtag: device not found!
    Error: esp_usb_jtag: failed to revive USB device!

    in reply to: Esp-idf 4.4/ ESP32-S3 #32331
    ya3
    Participant

    Whoops, didn’t even notice. Extended to a year from now!

Viewing 5 posts - 1 through 5 (of 5 total)