infineon4engineers Facebook

infineon@google+ Google+

infineon@linkedin linkedin

infineon4engi@twitter twitter

infineon@youtube youtube

Dave

+ Reply to Thread
Page 2 of 2 FirstFirst 1 2
Results 11 to 17 of 17

Thread: Application Kit TC2X7 - Flashing not possible after testing an example from hightex

  1. #11
    New Member New Member Enigma_ is on a distinguished road
    Join Date
    Jul 2016
    Posts
    1
    Points
    20
    Hi

    I have the same Problem and I wonder whether I could use the miniWiggler V3 to take the TLF35584 out of failsafe mode.
    I did not purchase it yet, that is why I did not already try it.
    Does anyone have experience on that?

    Regards
    Florian

  2. #12
    Beginner Beginner TASKING.hp.glas is on a distinguished road
    Join Date
    Mar 2015
    Posts
    30
    Points
    335.625
    Quote Originally Posted by Enigma_ View Post
    Hi

    I have the same Problem and I wonder whether I could use the miniWiggler V3 to take the TLF35584 out of failsafe mode.
    I did not purchase it yet, that is why I did not already try it.
    Does anyone have experience on that?

    Regards
    Florian
    Hi Florian,

    It’s possible I think, but maybe someone else wishes to chime in, in case I’m off. Earlier in this thread I mentioned that application note AP32260 (logon to myinfineon first) explains two solutions. One we already discussed. The other is by means of a PLS/Lauterbach debugger script that configures the CPU for SPI as a means to disable TLF35584. Those scripts are included in the application note plus a detailed explanation. Using this approach the mini-wiggler is only a means to an end. Of course either debugger must support it, which I suppose they do.

    Henk-Piet Glas
    Technical Product Specialist

  3. #13
    Hi,

    I'm asking if the mentioned solution will recover the TLF35584 and return it to its safe state and the microcontroller will function properly after that.
    or a permanent failure is occurred in the micro-controller which caused fail state by the regulator and the mentioned solution is intended to be used only in order to reflash the kit?

    Thanks
    Last edited by MohamedHasan; Sep 14th, 2016 at 06:08 PM.

  4. #14
    Beginner Beginner fheyde is on a distinguished road
    Join Date
    Nov 2016
    Posts
    2
    Points
    95
    Hello all,

    thank you for giving the hint with the Application Note 32260, Henk-Piet. I read through it completly. Since my Triboard Inverter Kit with Aurix TC264D and TLF35584 has an extensive grounded TM Pin, i am not able to connect that pin to 5V, neither to remove a resistor because there is none. So I chose the software solution with the PLS debugger. Since I use a differnt QSPI Modul and different Hardware Pins I changed the initialisation sequence as explained in the AP32260.
    Somehow if I try to connect the message pops up: Executing init commands failed.
    Maybe someone has an idea what is wrong in my code.

    SET 0xF0001D00 0x8 //Clock Control Register
    SET 0xF0001D10 0x03C04 //Globalcon
    SET 0xF0001D04 0x0 //PISEL
    SET 0xF0001D14 0x14000000 //GLOBALCON1
    SET 0xF0001D24 0x501 //ECON1 für slso1 und slso9
    SET 0xF0001D48 0x2000000 //SSOC

    SET 0xF003B000 0x00 //Port 10 Output Register initialisieren
    SET 0xF003B010 0x980000 //Serial Clock P10.2, P10_IOCR0
    SET 0xF003B010 0x98980000 //SDI P10.3, P10_IOCR0
    SET 0xF003B040 0x0 //Port 10 Pad Driver Mode 0 Register initialisieren
    SET 0xF003B044 0x0 //Port 10 Pad Driver Mode 1 Register initialisieren
    SET 0xF003B014 0x9000 //SCS P10.5 P10_IOCR4
    SET 0xF003B040 0x0 //Port 10 Pad Driver Mode 0 Register initialisieren
    WAIT 5
    SET 0xF0001D54 0xFFF //FLAGSCLEAR
    SET 0xF0001D60 0x97A10001 //BACONENTRY
    SET 0xF0001D10 0x01003C04 //GLOBALCON


    SET 0xF0001D64 0x8756 //DATAENTRY, write first spi word
    WAIT 5
    SET 0xF0001D54 0x200 //FLAGSCLEAR
    WAIT 5
    SET 0xF0001D54 0x400
    SET 0xF0001D64 0x87DE
    WAIT 5
    SET 0xF0001D54 0x200
    WAIT 5
    SET 0xF0001D54 0x400
    SET 0xF0001D64 0x86AD
    WAIT 5
    SET 0xF0001D54 0x200
    WAIT 5
    SET 0xF0001D54 0x400
    SET 0xF0001D64 0x8625
    WAIT 5
    SET 0xF0001D54 0x200
    WAIT 5
    SET 0xF0001D54 0x400
    SET 0xF0001D64 0x8D27
    WAIT 5
    SET 0xF0001D54 0x200
    WAIT 5
    SET 0xF0001D54 0x400
    SET 0xF0001D64 0x8A01
    WAIT 5
    SET 0xF0001D54 0x200
    WAIT 5
    SET 0xF0001D54 0x400
    SET 0xF0001D64 0x87BE
    WAIT 5
    SET 0xF0001D54 0x200
    WAIT 5
    SET 0xF0001D54 0x400
    SET 0xF0001D64 0x8668
    WAIT 5
    SET 0xF0001D54 0x200
    WAIT 5
    SET 0xF0001D54 0x400
    SET 0xF0001D64 0x877D
    WAIT 5
    SET 0xF0001D54 0x200
    WAIT 5
    SET 0xF0001D54 0x400
    SET 0xF0001D64 0x8795 //DATAENTRY write last SPI Word
    WAIT 5
    SET 0xF0001D54 0x200
    WAIT 5
    SET 0xF0001D54 0x400

    Regards
    Felix

  5. #15
    I appreciate the Technical Product Specialist. very cooperative.. other than I have faced this problem, you solved quickly

  6. #16
    Beginner Beginner TASKING.hp.glas is on a distinguished road
    Join Date
    Mar 2015
    Posts
    30
    Points
    335.625
    Quote Originally Posted by Camryn64 View Post
    I appreciate the Technical Product Specialist. very cooperative.. other than I have faced this problem, you solved quickly
    Hi Camryn64,

    Thanks very much for saying that. FYI, recently I was doing some tests using Infineon memtool, and I found that it has a "execute initialisation commands on reset" menu item. In addition I noticed that it already contains some commands that start with this comment:

    ; Workaround for TLE35584 A-Step Bug

    So presumably connecting with memtool will disable the watchdog and restore the connection to your board. You'd then somehow need to add that same workaround into the startup code of your application.

    The startup code makes a callback to function _call_init() which you may populate for yourself with user initialisation code, for example the above workaround. To make sure the startup code actually calls this function you need to enable preprocessor macro __CALL_INIT. To make sure you timely meet feeding the watchdog, you may need to reposition _call_init() to an earlier point in time; at this point it's called prior to calling the main entry point. This way you should be able to use the TASKING debugger to debug your application.

    Of course the hardware workaround still holds as well, with the added advantage that you needn't make changes to your code.

    Best regards,

    Henk-Piet Glas
    Technical Product Specialist

  7. #17
    Beginner Beginner mrbhinder is on a distinguished road
    Join Date
    Nov 2017
    Posts
    4
    Points
    80
    Hi,

    I have TC2X4 Application kit. i tried the same procedure i.e. removed R128 and place it at R127. But no fortune.
    I saw someone else had the same problem and he created a thread about it but the thread has no replies. Please guide, what can i do to solve this problem?

    Best Regards,

    Usman

+ Reply to Thread
Disclaimer

All content and materials on this site are provided “as is“. Infineon makes no warranties or representations with regard to this content and these materials of any kind, whether express or implied, including without limitation, warranties or representations of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, whether express or implied, is granted by Infineon. Use of the information on this site may require a license from a third party, or a license from Infineon.


Infineon accepts no liability for the content and materials on this site being accurate, complete or up- to-date or for the contents of external links. Infineon distances itself expressly from the contents of the linked pages, over the structure of which Infineon has no control.


Content on this site may contain or be subject to specific guidelines or limitations on use. All postings and use of the content on this site are subject to the Usage Terms of the site; third parties using this content agree to abide by any limitations or guidelines and to comply with the Usage Terms of this site. Infineon reserves the right to make corrections, deletions, modifications, enhancements, improvements and other changes to the content and materials, its products, programs and services at any time or to move or discontinue any content, products, programs, or services without notice.