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.

AM6422: BISS Request cycle on sdk11

Part Number: AM6422
Other Parts Discussed in Thread: SYSCONFIG

 

https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1359937/mcu-plus-sdk-am243x-biss-c-maximum-requiest-cycle/5194126?tisearch=e2e-sitesearch&keymatch=BISS%20maximum#

 

The solution to  change biss_drv.c works well up to SDK9.2

pruicss_xchg->delay_40us          = ((icssgclk*10)/1000000); change to 10us

With solution above, i am able to achieve BiSS request of 62.5us

 

Using the latest motor_control_sdk_am243x_11_00_00_06 , I ported biss_drv.c and biss_master.asm and make similar change. However it seem the solution above no longer effective.  I can not achieve 62.5us request cycle with latest code from motor_control_sdk_am243x_11_00_00_06.

 

Is there any section that I can change to achieve 62.5us request cycle

 

Thank you

Alan I

  • HI Alan,

    can you send me the signal capture of BiSS-C RX and CLK lines?
    Things I want to understand here is
    1. What is BiSS-C CLK Freq
    2. What's the cycle time with current configuration

    Thanks
    Arnav 

  • Hello Arnav

    Thank you for the reply. I do not have access to the Signal capture setup this week.

    I have found a mistake on my part , with the fix the BiSS-C is now able to acquire position in 62.5us but only with 8Mhz SPI clock.

    Going back to BiSS Diagnostic, I found that the  BiSS-C position acquisitions are always producing CRC Error  with BISS clock  of 5Mhz and 10Mhz using example from SDK11

    Result with 5Mhz BISS-C clock - CRC failed


    Encoder-1 Singleturn Angle: 44.914207458000, received safety crc:0x7ffe, calculated safety crc:0xc9c6, e_w:0x0, sign-of-life counter: 14

    CRC Status: failure, crc error count: 26

    Encoder-2 Singleturn Angle: 349.375427246000, crc:0x3f, otf crc:0x2a, e_w:0x1

    CRC Status: failure, crc error count: 26

    Channel 1:

    Encoder-1 Singleturn Angle: 163.011367798000, crc:0xb, otf crc:0x9, e_w:0x0

    CRC Status: failure, crc error count: 26

    Result with 8Mhz BiSS-C clock- CRC matches


    Encoder-1 Singleturn Angle: 44.914207458000, received safety crc:0x7ffe, calculated safety crc:0xc9c6, e_w:0x0, sign-of-life counter: 14

    CRC Status: failure, crc error count: 26

    Encoder-2 Singleturn Angle: 349.375427246000, crc:0x3f, otf crc:0x2a, e_w:0x1

    CRC Status: failure, crc error count: 26

    Channel 1:

    Encoder-1 Singleturn Angle: 163.011367798000, crc:0xb, otf crc:0x9, e_w:0x0

    CRC Status: failure, crc error count: 26

    I repeat the test with both 200Mhz and 300Mhz PRUICSSG clock

     Failures with 5Mhz and 10Mhz BiSS clock  are not show stopper for us for now and we are able to the BiSS-C with 8Mhz Clock

    Thank you

    Alan I

  • Hi Alan, 

    I think the crc issue might be due to rx source clock selection. You can check in sysconfig. 




    Check this page for supported rx clock & over sampling rate combination

    software-dl.ti.com/.../BISS-C.html

    Thanks
    Arnav

  • Hi Alan,

    any news on this?

    Thanks
    Arnav

  • Hi Arnav

    Sorry for the delay, I was out sick

    Using Endat Diagnostic , I tested the CONFIG_BISSC0_TX_RX_FIFO_CLOCK_SOURCE with 0 & 1 at BiSS Clock 4/5/10/  Mhz and  the result+CRC seems to match the table you provided

    Thank you

    Alan I