Categories

Recently modified/created topics
Arm Cortex-M: Error 304: Check Debug Adapter 14-Jan-2025
Error 304 means the BlueBox fails to connect and establish a debug session with theCortex-M-basedtarget CPU. Possible solutions Use the Reset debug command When troubleshooting the initial debug connection to the target CPU, it's recommended to use the CPU Reset debug command instead of th...
BlueBox comparison 14-Jan-2025
The iC7 BlueBox Comparison table display s the features and differences of the iC7mini, iC7pro, and iC7max BlueBox. The iC5BlueBox Comparison table compares the iC5700 and iC5000 BlueBox.
Using older and newer USB drivers side by side 09-Jan-2025
It is possible to selectively decide which hardware is used with which driver (e.g. use an old, proprietary driver for iC3000GT and winUSB driver for iC5700). Possible solution 1. Make sure that the winUSB is used for the desired hardware. 2. Connect the hardware you wish to associate with...
Dedicated placement of ROM copy sections for initialized data 07-Jan-2025
This article is for the TriCore toolset. A similar approach applies to our other toolchains as they use the same linker script language. When a variable is initialized as shown below, the initialization value for this variable needs to be placed in flash memory : int var_1 = 10; The linker...
Memory usage information included in a map file 07-Jan-2025
The available on-chip memory of an Infineon AURIX family derivative is distributed across various memory areas. You need to be aware of the extent to which the application code and data use individual memory ranges. This can indicate potential bottlenecks that may require you toadjust the ...
Change the section attribute at link stage / prevent initialization of sections 07-Jan-2025
This article is for the TriCore product. A similar approach applies to our other products as they use the same linker script language. The C compiler adds section attributes to all code and data sections it creates. The available section attributes are:  r readable sections w writable sec...
Linker Warning W132: cannot bind symbol _lc_ub_heap … and cannot bind symbol _lc_ue_heap … 07-Jan-2025
The cause of these warnings after upgrading to v6.3r1 is that the heap definition was moved from tc_mc_arch.lsl to derivative .lsl to support core-specific LSL files, where each core has its own heap. The tc_mc_arch.lsl file is now included in derivative .lsl . Possible solutions When the ...
Debugger Error: Loading failed: A problem occurred during downloading 07-Jan-2025
When your application is fully located in RAM, the debugger may fail to download and run it on the target. In that case, the debugger issues an error: Loading failed: A problem occurred during downloading Possible solution Certain parts of the internal memory are automatically cleared duri...
User stack size calculation in the map file shows zero-sized stacks after upgrading to TriCore v6.3r1 07-Jan-2025
Possible solution In TriCore v6.3r1, the entry_points keyword was introduced to specify different entry points for the stack size calculation. If those entry points are not defined, the map file will show a stack size of zero bytes in the 'Estimated stack usage' section like: * Estimated s...
Symptoms of a stack overflow in a TriCore application 07-Jan-2025
Typically a stack overflow will show: a strange behavior of the application and/or a subsequent out-of-control behavior (crash/application trap). The post-mortem analysis will have to include an inspection of the stack pointer (A10 register), the trap status register, and possibly a trace ...