Legacy microcontrollers Forum Discussions

Greetings

im looking to hire someone who will be able to read/write specific automotive engine ecu which mounts password protected infineon tricore tc17xx microcontroller

currently no tool on the market offer support for this ecu type,

i am aware its complex job but i am interested to solve, price is not an issue if it can be solved, i have alot of these units waiting,

 

best regards

Show Less

Hello.

[1] chapter 8.14.3.1 states "The ECC error detection can be triggered on purpose to test the detection itself and the associated trap routine. This test option is available for RAMs". So, previous stated chapter describes how the RAM ECC error detection can be tested. That’s fine.

My question: How can the flash ECC error detection be tested?
Question reason: In [1] chapter 3.10.7.1 I see the flash ECC description. But I don’t find in [1] a chapter for the flash, which is similar to (above stated) [1] chapter 8.14.3.1.

Regards
Oliver.

References:
[1] https://www.infineon.com/dgdl/xe166h_um_v1.1_2009_04.pdf?fileId=db3a304328c6bd5c01291210b0cb099d

Show Less

We are using S6E2CCAL0AGL2000A in our project. It was working fine. But suddenly unable to flash new program and while flashing new program, controller is getting reset automatically through Jlink without program getting updated in controller

Show Less

I am trying to understand this Assembly macro that sets the stack pointer to the location of a Task Stack of a RTOS. There are a few Assembly commands that I don't know and where I can't find that much information of.

This code points the User stack pointer to the stack of a Micrium Task (uC/OS III RTOS). But these tasks are only allowed to lay into near memory, and that is probably because of these assembly functions.

That's why I'm trying to find out what exactly is happening here. And why the stack can only be in near memory. After that I would like to find out if I can rewrite this to support tasks stacks outside of the near memory.

This assembly code is running on a XE169 chip (C166 Family):

LOAD_USRSTK_PTR .MACRO
    EXTP    #PAG _OSTCBHighRdyPtr,#02h    ; R4/R5 = OSTCBHighRdyPtr
    MOV     R4,POF _OSTCBHighRdyPtr
    MOV     R5,POF (_OSTCBHighRdyPtr+2)

    EXTP    R5,#01h                       ; user stack ptr = OSTCBHighRdyPtr->OSTCBStkPtr
    MOV     R15,[R4]
.ENDM

This is how far I've found out what each line of code does:

LOAD_USRSTK_PTR .MACRO

Start of macro with the name LOAD_USRSTK_PTR

EXTP    #PAG _OSTCBHighRdyPtr,#02h

Begin Extended Page Sequence, the next 2 instructions are part of the Extended Page Sequence

What does the #PAG _OSTCBHighRdyPtr part in this instruction mean, does this get the Page part of of the address where OSTCBHighRdyPtr is pointing to.

MOV     R4,POF _OSTCBHighRdyPtr

Write _OSTCBHighRdyPtr into Register 4. What does POF mean in this instruction, does it get the value of the pointer and store that in Register 4?

MOV     R5,POF (_OSTCBHighRdyPtr+2)

Write the value of at 2 addresses further as the address of OSTCBHighRdyPtr to Register 5. What does POF mean in this instruction Is it in this case copying the ExtPtr address? because this address is 4 bytes long, and the Register only 2 bytes?

EXTP    R5,#01h                       ; user stack ptr = OSTCBHighRdyPtr->OSTCBStkPtr

Begin Extended Page Sequence. Next 1 instruction is part of the Extended Page Sequence. R5 = Register 5 what exactly is done with this register

MOV     R15,[R4]

Move the value of Register 4 into Register 15, R15 is the User Stack Pointer

.ENDM

End of Macro

The _OSTCBHighRdyPtr is a pointer to a struct, the (beginning) of this struct looks like this:

struct os_tcb {
    CPU_STK      *StkPtr;         /* Pointer to current top of stack                  */
    void         *ExtPtr;         /* Pointer to user definable data for TCB extension */
    CPU_CHAR     *NamePtr;        /* Pointer to task name                             */
    CPU_STK      *StkLimitPtr;    /* Pointer used to set stack 'watermark' limit      */
    ....
}

CPU_STK is a typedef of unsigned short __near.

The sizes of the items in this struct are:

StkPtr = 2 bytes (in near memory thus 2 bytes is enough)
ExtPtr = 4 bytes
NamePtr = 4 bytes
StkLimitPtr = 2 bytes (in near memory thus 2 bytes is enough)

Show Less

Hi.

I met a problem during DAS installation on windows 7.

POP-up window(Run-time errors in the installation script) was appeared like attached screen shot.
I don't know the reasons.
Someone help me please.


Regards. Show Less