Forum Replies Created

Viewing 15 posts - 1 through 15 (of 31 total)
  • Author
    Posts
  • ConnorConnor
    Keymaster
    Post count: 31

    Hi Justin,

    If you flashed the default binary from the sample, the application software likely will not show anything on CAN2. To make sure your flashing bootloader is still intact, try initiating a new flash within 1-3s of powering up the device.

    ConnorConnor
    Keymaster
    Post count: 31

    Hi Kantesh,

    It does look like there is some forbidden operation happening in the CAN interrupt logic.

    – Is the CAN traffic when you are in this specific state of DC charging?
    – Are all of your CAN reads handled by interrupt or do you have a mix of polling and interrupt?
    – While in this specific state of DC charging, are you running an operation that blocks for a long time, creates it’s own interrupts, or disables other interrupts?

    ConnorConnor
    Keymaster
    Post count: 31

    Hi Mathew,

    Did you flash your application software over CAN or over JTAG?

    ConnorConnor
    Keymaster
    Post count: 31
    in reply to: JTAG #19320

    JTAG flashing and debugging is not officially supported without a proprietary adapter, which requires an additional “developer” agreement between your company and Audesse. If you require this feature, please reach out to the team directly to start the process.

    ConnorConnor
    Keymaster
    Post count: 31

    Is the CAN bus terminated?

    ConnorConnor
    Keymaster
    Post count: 31

    – The diagnostic buzzer is not present on the FlexCase E, thank you for pointing out a mistake in the guide, I will fix promptly.

    – The error in your screenshot indicates that your computer does not recognize the peakCAN device. Did you install the peakCAN drivers mentioned in the Prerequisites for the tutorial?

    ConnorConnor
    Keymaster
    Post count: 31

    This is not related to disabling wake-on-CAN, please see this thread instead:

    ConnorConnor
    Keymaster
    Post count: 31

    I will also reference the duplicate thread in the NXP forums:
    https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/FreeMaster-not-connecting-over-CAN-MBDT-1-5-S32K344/m-p/1886702.

    I have attached an example of FreeMaster over CAN working on FCE/FCG CAN0 in case you don’t have it already. We are not officially supporting MBDT 1.5 yet since we need to re-validate our sample software, but I am guessing there is a small bug somewhere in your mex file that is preventing other busses from working. For example, from the NXP forum screenshot, the name of the CAN controller for CAN2 has the same name as CAN0, which could be causing problems. Please review the differences between your mex file and the one I posted here, and I can review potential problems.

    Attachments:
    You must be logged in to view attached files.
    ConnorConnor
    Keymaster
    Post count: 31

    The GPIO12/GPIO13 pins are internal gpio mapping from the Raspberry Pi CM4, not Radxa. The datasheets have been updated to reflect the two sets of pins compatible with MPU UART5 (pins 28/31 for Raspi, pins 62/57 for Radxa CM3). The standard/focus SKU for FCE2.1 has both sets of pins populated, but if you have an alternate SKU, the Radxa-compatible pins may not be populated.

    ConnorConnor
    Keymaster
    Post count: 31
    in reply to: CAN Flasher Bug? #18848

    It looks like you’re looking in the folder you used to install the program, not the program files directory listed in the tutorial. The configs should be in C:/Program Files/FlexCaseFlash/resources/flashconfigs unless you specifically chose a different install directory.

    ConnorConnor
    Keymaster
    Post count: 31

    Hi Craigbeal,

    In addition to the information above:

    Please find the link to the datasheet https://www.audesseinc.com/resources/datasheet/?model_sku=FlexBench+1.2&fusion-form-nonce-17520=f102ce5f7b

    In the datasheet, when the mouse pointer is hovered over each pin, the GPIO name (shown in red) pops up and its corresponding connector pins (shown in yellow box), Breakout board (shown in green box) is listed.

    Please let me know if this clarifies your query or incase otherwise please let me know.

    Thanks
    Sandeep Jayabal

    • This reply was modified 6 months ago by ConnorConnor.
    Attachments:
    You must be logged in to view attached files.
    ConnorConnor
    Keymaster
    Post count: 31

    Hi craigbeal,

    Please find the information below:

    The Digital inputs can be configured for Pull up / pull down based on requirements using the (hardware) DIP switch. It is not software configurable for FCB 1.2.

    Toggle the “MPU DI-10K-PD” for pull down configuration and “MPU DI-10K-PU” for pull up configuration. (shown in the image)

    Kindly refer to the digital input guide https://www.audesseinc.com/resources/digital-input-guide/ for additional details

    Please do let me know for any further support

    Thanks
    Sandeep Jayabal

    Attachments:
    You must be logged in to view attached files.
    ConnorConnor
    Keymaster
    Post count: 31

    Hi craigbeal,

    Please find the information that you were looking for in our webpage.

    Link: https://www.audesseinc.com/resources/digital-input-guide/

    Let us know for any further questions

    Thanks
    Sandeep Jayabal

    ConnorConnor
    Keymaster
    Post count: 31

    Hi craigbeal,

    Thanks for raising this concern,

    We are currently working on this information and we will get back to you with the Digital Inputs webpage for your convenience at the earliest.

    Thanks
    Sandeep Jayabal

    ConnorConnor
    Keymaster
    Post count: 31

    Hello Kantesh,

    Please use the PTB19 for the EN_Lin.

    Thanks
    Sandeep

Viewing 15 posts - 1 through 15 (of 31 total)