LIN unified Bootloader using ECU Bus

[Asharm11]

I had downloaded the unified_bootloader_demo_v2.1 which contains demo applications of bootloader.

I want to use LIN S32K142 bootloader, but the demo project does not contain the project for LIN S32K142, so I converted the LIN S32K144 project to LIN S32K142. On flashing the bootloader project on the NXP S32K142 100 pin board, the LED pins toggle but we get the following error on ECU bus tool.

What should be done to resolve this?

[Nxp_Vishal]

@nxf10035 

Greetings!!!

I am using S32K324 controller. I have developed non-UDS application. 
I want to use bootloader software to flash non-UDS applicaiton.

[Query]
Is it possible to use unified bootloader [S32K324_CAN_Bootloader_RTD2d0 & ECU bus GUI] to flash non-UDS application? If yes, what software updates I will have to make in [S32K324_CAN_Bootloader_RTD2d0 & ECU bus GUI]?

[nxf10035]

Hi, @Nxp_Vishal 

      Currently, unified bootloader and ECU-BUS only support UDS. 

BR

Tomlin

[pratibhasurabhi]

Hi Tomlin,

Is it necessary to have UDS implemented in the application code to be flashed . As per my understanding once bootloader code is flashed we can flash application code via ECU bus using bin file even though UDS is not implemented in that .Please confirm my understanding .

[nxf10035]

Hi, @pratibhasurabhi 

     If APP running, need to update new APP version. APP received UDS command and back to bootloader. So, the UDS is needed in APP.

BR

Tomlin

[nxf10035]

Hi, @Asharm11 

      From your picture, I see that you only select download file process. Please note, the step as following:

1. Import process(JSON)

2. Connect hardware and config LIN node information

3. Select address of ECU BUS

For how to use the ECU-BUS, you can reference the user guide of ECU_BUS.

Suggestion you can open PLIN view and check the log of LIN BUS. It's better to upload the log when you met problems.

BR 

Tomlin

[Asharm11]

Hello @nxf10035 

I followed what you said and i have been referring the ECU bus User guide there is nothing for how to use UDS on LIN and the error remains intact 

so can we have a meeting regarding this issue 

I am sharing the PLIN view Image as well as current error's image

[nxf10035]

Hello, @Asharm11 

     From your picture, it seems the TX LIN ID un-correct. The ECU-BUS TX LIN ID should 0x3C and RX LIN ID is 0x3D.  

BR

Tomlin

[Asharm11]

Hello @nxf10035  

I changed the TX and RX ids to 3C and 3D respectively but I am getting the same result

I am attaching the snapshot for ECU bus tool setting and LIN tp settings 

thank you 

Abhishek

[nxf10035]

Hi, @Asharm11 

   From my side working normally via S32K144 EVB. Attachment are the log and configuration of ECU-BUS(0.2.23). Please reference.

BR

Tomlin

[Asharm11]

hello @nxf10035 ,

I tried with the IDs provided by you but I am getting the same error 

and I am using the ECUBUS tool(0.2.13) ,could that be the issue?

I am attaching the snapshots of LIN TP settings

your thoughts would be appreciated

Thank you 

Abhishek 

[nxf10035]

Hi, @Asharm11 

    Suggestion you update ECU-BUS tool version to 0.2.23.

BR

Tomlin

[Asharm11]

Hello @nxf10035 ,

I used ECUBUS tool (v0.2.23) and still getting the same error "[4935ms][sch1]{"msg":"No response","index":1}"

could you please help me with it and Could you tell me how to generate the log file as well 

Thank you 

Abhishek

[nxf10035]

Hi, @Asharm11 

     The log captured by PLIN-View Pro. The test step:

1. Open ECU-BUS and connect PCAN(LIN)

2. Open PLIN-View Pro and capture the LIN log

3. Click Start of ECU-BUS

Please note: before test should connect LIN BUS including GND, VBAT and LIN. If you test failed, please upload the LIN log captured by PLIN-View Pro.

BR

Tomlin

[Asharm11]

hello @nxf10035 

I am able to generate the log file but in itrc format i am sharing the log file with you but the error remains 

sharing the ECU bus tool error snapshot as well 

Thanks 

Abhishek 

[nxf10035]

Hi, @Asharm11 

    From your LIN log the ECU-BUS working normally. The UDS message has been sent to LIN BUS. Suggestion you check LIN configuration of ECU side:

1.  Baud Rate

2. I/O as LIN feature

3. Debug ECU side received LIN messages or not

4. Hardware connect

BR

Tomlin

[Asharm11]

Hii @nxf1003

I have checked the baud rate it was 19200 bps

hardware is connected properly 

still I am getting the no response error as shown in the attached snapshot

your help would be appreciated

Regards

Abhishek

[nxf10035]

Hi, @Asharm11 

    From my side, some suggestion as following:

1. Check hardware LIN(LPUART instance) and software configure is the same or not

2. Baud rate

3. Hardware connect including: LIN, VBAT and GND

4. Check LIN transceiver configuration

4. If above all is correct, you can capture the LPUART RX and TX signals over oscilloscope. If oscilloscope have not anything signals, then the issue might be from hardware. If the RX line have signals, then check the LIN driver RX the data or not. This can set a breakpoint in LIN RX ISR.

BR

Tomlin

[Asharm11]

Hello @nxf10035,

I updated the ECU bus too to v0.2.24 and now I am getting this error"[4970ms][sch1]{"msg":"No response","index":1}" attaching the snapshot 

and could you tell me how you generated the log file 

Regards

Abhishek

[nxf10035]

Hi, @Asharm11 

   Please test over ECU-BUS(0.2.23).

BR

Tomlin

[Asharm11]

Hello @nxf10035 ,

I tried updating it with ECU Bus tool update feature but seems to not responding so could you please help me with update link of the Ecu bus tool.

Regards,

Abhishek