Search:

Type: Posts; User: rswindell

Search: Search took 0.00 seconds.

  1. Success!

    I also created an Altium/TASKING support request to see if there is a linker script equivalent and received this helpful response:


    With this adjustment to the linker script, I can use that...
  2. Success! I found this little blurb in the 1200...

    Success!

    I found this little blurb in the 1200 page TASKING tools manual:

    #pragma section const_init
    Sections with constant data are copied from ROM to RAM at program startup.

    That's the...
  3. More information: I've tried "section...

    More information:

    I've tried "section renaming" to get these numeric constants (.zrodata.*) into the DSPR or PSPR by adding to FlashDemo.c:


    #pragma section farrom dspr0
    #pragma section...
  4. We received the following explanation from an...

    We received the following explanation from an engineer at Infineon with regards to the non-zero values in erased PFlash sectors:



    Why Memtool reports these erased PFlash sectors as "not empty"...
  5. Update: I think I may have identified the...

    Update:

    I think I may have identified the problem (but not the solution). Here is the exact instruction at the location of a trap that occurs while erasing the PFlash from the TriCore PSPR...
  6. Update: I misspoke when I wrote "If I copy...

    Update:

    I misspoke when I wrote "If I copy this code to the PSPR first and execute from there, there is no difference in behavior.". The code does have to be copied to and executed from PSPR or...
  7. Update: By using the UDE Starterkit Debugger...

    Update:

    By using the UDE Starterkit Debugger by PLS, I can now see that the Infineon FlashDemo code is entering trapcontext() when attempting to modify the PFlash sector.

    Some time after...
  8. I've whittled the code down from Infineon to just...

    I've whittled the code down from Infineon to just this little bit:

    static void FlashDemo(void)
    {
    uint16 endinitSfty_pw;
    uint32 sector_addr = 0xaf008000;

    endinitSfty_pw =...
  9. Here's another clue: If I read the Flash Status...

    Here's another clue:
    If I read the Flash Status Register (FSR) just before the read of the PFlash (where the PFlashDemo halts), I get the value 0x01002000, that's bits 24 (RES) and 13 (PROER) set.
    ...
  10. More details: building FlashDemo.hex using the...

    More details: building FlashDemo.hex using the IfxFlash.c/h from AURIX iLLD Package v1.0.1.0.0.zip -> iLLD_1_0_1_0_0\Src\BaseSw\iLLD\TC27D\Tricore\Flash\Std\ made no difference in the FlashDemo...
  11. Problems with erasing and programming PFlash on AURIX TriCore (tc0), TC277-DC

    Questions regarding use of Infineon - Memtool (v4.07.03) with TC277-DC:

    1. After using the "Erase..." option to erase a sector of PFlash (PF0), if I subsequently use the "Read..." option to read...
  12. Any resolution to this question? Thank you, ...

    Any resolution to this question?

    Thank you,

    -Rob
  13. Questions reg; Infineon Software Framework and iLLD package using TASKING tools

    We have an "Infineon AURIX TriBoard TC277 Starter Kit". The included printed documentation states the micrococontroller is a TC277T. The cardboard box says it's a "KIT_AURIX_TC277_S_TRB DC-STEP with...
Results 1 to 13 of 13
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.