• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 31 subscribers
  • Views 434 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.

LP-AM243: BiSSC project - Switch ICSSG

Ariel Ronen
Prodigy 220 points
Part Number: LP-AM243
Other Parts Discussed in Thread: SYSCONFIG

Tool/software:

Hi,

I'm trying to run the BiSSC project from SDK 09.02.00.09 I'm using the following projects:

1. bissc_diagnostic_single_channel_am243x-lp_r5fss0-0_freertos_ti-arm-clang

2. bissc_peripheral_interface_single_ch_am243x-evm_icssg0-pru1_fw_ti-pru-cgt

I've been trying to swap the ICSSG: Previously is was ICSSG0_PRU1 and I want to switch to ICSSG1_PRU0.

I've made all the necessary changes + change the project defines in 'bissc_peripheral_interface_single_ch_am243x-evm_icssg0-pru1_fw_ti-pru-cgt'.

Sadly, I fail to get the acknowledge signal:

I would like to request you assistant in the matter.

Thanks,

Ariel

  • 0
    TI__Prodigy 400 points

    Hi Ariel,

    Just a quick check list of changes before we proceed 

    1. Changes in project specs for firmware ( as you have mentioned) 

    2. Changes in examples\position_sense\bissc_diagnostic\single_channel\am243x-lp\r5fss0-0_freertos\example.syscfg file using sysconfig gui 
     

        a) update the ICSS instance and PRU Slice 

        

       b) update BISSC_CH0_OUT_EN & BISSC_CH2_OUT_EN GPIO pins as per the PRU slice & Instance



       


    If you have done these changes and it's still not working then we can further debug this issue. Meanwhile you can try to capture BiSS-C signals and share the traces. 

    Best Regards 
    Arnav



            

  • 0 in reply to Arnav Raj
    Prodigy 220 points

    I have done this already and still does not run.

  • 0 in reply to Arnav Raj
    TI__Expert 3802 points

    Hi Arnav,

    Thanks for your support!

    As customer has done all your mentioned above, but still not working, this is quite urgent at customer side.

    May I know what could be the next steps to further analyze?

    Many Thanks,

    Kevin

  • 0 in reply to Kevin Peng
    TI__Prodigy 400 points

    Hi Kevin, 

    We can try below mentioned things as next steps

    1. Try to capture the clk and data signal for BiSS-C and share the trace file. We can analyze the traces to detect what can be the problem. 

    2. Try to debug the firmware and see where exactly firmware is getting stuck. 

    3. Check if tx_enable signal for channel is set up correctly.


    Best  Regards 
    Arnav 

  • 0 in reply to Arnav Raj
    Prodigy 220 points

    When you try to make the changes on your side it works? I find it very confusing when I'm just trying to make changes on your example project.

    Let me show you what I was doing:

    1. for the PRU Project:

    2. ARM project:

    a. SysConfig:

    Note - I had to leave BISSC0 because of your internal bug where you can't define ICSSG1 without defining ICSSG0 - I encountered the same issue before with the SDFM.

    b. code:

    Changes all CONFIG_BISSC0_xxxxx to CONFIG_BISSC1_xxxxx

    Change 'bissc_receiver_bin.h' to match the new output from the PRU project.

    This is where I get error:

    Basically - pruicss_xchg->cycle_trigger[0] is never 0.

  • 0 in reply to Ariel Ronen
    TI__Prodigy 400 points

    Hi Ariel, 

    Currently I don't have the requisite hardware to test for ICSSG1_PRU0. And I can't use the existing one due to pin out requirements.


    In answer to your sysconfig configuration when you add CONFIG_BISSC0 & CONFIG_BISSC1 both  two PRU_ICSS configuration namely  CONFIG_PRU_ICSS0 & CONFIG_PRU_ICSS1 for ICSSG0 & ICSSG1 respectively are created.  

    PRUICSS_open() api in application c file is called with CONFIG_PRU_ICSS0 as parameter which you have to update to CONFIG_PRU_ICSS1. 

    Ariel Ronen said:

    Note - I had to leave BISSC0 because of your internal bug where you can't define ICSSG1 without defining ICSSG0 - I encountered the same issue before with the SDFM.

    In answer to this I'm using sysconfig 1.20.0 and i'm not seeing this issue. 
    can you crosscheck this again? are you not able to add instance as ICSSG1 in CONFIG_BISSC0?