• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 31 subscribers
  • Views 1305 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

(usb_dev_bulk.c) calls to USBLIB 2.1.2.111 cause compiler v5.2.7 warnings.

Genatco
Guru 56083 points


Hello USB configurators -- past have fixed this very same warning from earlier versions of USBLIB.

Same (usb_dev_bulk.c) module does not cause warnings in project using older library 2.1.0.12573 and same compiler v5.2.7. 

Seem to recall fixing something in USBLIB to make (tUSBBuffer) uint8_t character buffer compatible but don't remember what or where did too make patch.

BTW: There is a required (usb_dev_bulk) #define missing from "foggy from Wednesday" 2.1.2.111 (usblib.h).

  • 0
    TI__Guru**** 244440 points
    Hello BP101

    There was a change in the manner the data exchange for the USB Library call are made in TivaWare 2.1.1.71 onwards

    Regards
    Amit
  • 0 in reply to Amit Ashara
    Guru 56083 points
    Hi Amit,

    Recall the same warnings for porting 8 bit CHR complain being 32 bit even in earlier library but somehow fixed it too. USB port is pushing 450KBPS into 8 bit USB buffer writes is smoking fast. Data transfers running 250KBPS average piped into Windows virtual serial driver has what seems are rare but random perhaps speed related issues in the bulk transport layer.

    BTW: Can you see the *.jpg above post is showing only an Xbox on this end and did the same for *.png until changed post above to a *.jpg??
  • 0 in reply to Genatco
    TI__Guru**** 244440 points
    Hello BP101

    No, I do not see a jpg or png

    Bulk on FS have a speed restriction in terms of overhead and payload possible.

    Regards
    Amit
  • 0 in reply to Amit Ashara
    Guru 56083 points

    Hi Amit,

    Ok speed restriction would be necessary for 32 bit buffer writes, seemingly not a problem for 8 bit writes. May not need to separate USB apps from data port variables sent via IP stack, LWIP memory semaphores was culprit for long lived random buss faults appearing in protected memory areas. May revisit USB host hub IOT manager - that was a bit advanced for me at this point. 

    Perhaps try semaphore 1 on the 18 day fault launch pad, assumed you were inferring an IOT connection. You can accelerate bus faults condition making TM4c1294 Systick divisor (sysclk/200) versus (sysclk/100).

    Something may be broken as forum page will not show (png/jpg) attachments, logon prompt top of page missing along with post edit drop down.

  • 0 in reply to Genatco
    TI__Guru**** 244440 points
    Hello BP101

    Yes, it seems something is broken as forum users today have complained about unable to upload zip files as well

    Regards
    Amit