Microcontrollers

Hello,

I'm using ADS 1.2.2 and connecting to my proprietary target board containing TC277 with miniWiggler over DAP2. Compile and link is just fine.

My problem is that when I launch the integrated (TASKING?) debugger it takes approx. 5 minutes to open the debugger perspective. In the console it looks like it freezes:

Starting Debugger...

Launching configuration: Test
Loading 'I:\Eclipse\ADS\Debug\Test.elf'...

After 5 minutes, once the debugger is launched, it works just fine.

The five minute delay is variable depending on the performance of the PC being used. A slower laptop can take up to 10 minutes.

What is happening during this period please? Flashing the same program with MemTool and miniWiggler takes seconds as usual so doubt it is a slow flashing issue.

Any help to reduce this time would be very much appreciated.


Thanks. Show Less

I'm using TC397XE for this project where I'm trying to achieve basic Master-Slave communication between two I2C modules of TC397XE. I2C0 as Master and I2C1 as Slave.

I reached the point, where Master sends data, but doesn't receive respond from Slave (which should respond with Acknowledgement - SDA low during 9th SCL positive edge). I'm suspicious about Slave configuration settings, although cannot find the cause of problems. Here is Slave configuration code:

 

  /************************* I2C Module 1 => SLAVE *************************/
    
  /* Enable access for CLC */
  clearWdtEndinit();
  
  /* Clock enable for I2C1 module */
  I2C1_CLC.B.DISR = 0;              // Enable module
  while( I2C1_CLC.B.DISS == 1 );    // Wait while disabled
  I2C1_CLC1.B.RMC = 1;              // Clock division by 1
  while( I2C1_CLC1.B.RMC != 1 );    // Wait while disabled
  I2C1_CLC1.B.DISR = 0;             // Enable module
  while( I2C1_CLC1.B.DISS == 1 );   // Wait while disabled
  
  /* Configure protocol interrupts */
  I2C1_ERRIRQSM.U = 0;
  I2C1_PIRQSM.U = 0;
  I2C1_IMSC.U = 0;
  
  /* Disable I2C1 module */
  I2C1_RUNCTRL.B.RUN = 0;           // Configuration registers accessible
  
  /* Configure operation options */
  I2C1_ADDRCFG.U = 0;
  I2C1_ADDRCFG.B.ADR = I2C_config.slaveAddress;  // Address is given by this 
                                                 // struct
  I2C1_ADDRCFG.B.TBAM = I2C_config.addressMode;  // 7-Bit Address mode select
  I2C1_ADDRCFG.B.MnS = 0;                      // Module configured as master

  
  /* Configure FIFO settings */
  I2C1_FIFOCFG.U = 0;
  I2C1_FIFOCFG.B.RXFC = 1;     // RX FIFO as flow controller
  I2C1_FIFOCFG.B.TXFC = 1;     // TX FIFO as flow controller
  I2C1_FIFOCFG.B.RXFA = 0;     // RX FIFO Alignment - byte aligned 
  I2C1_FIFOCFG.B.TXFA = 0;     // TX FIFO Alignment - byte aligned
  I2C1_FIFOCFG.B.RXBS = 0;     // Burst size 1 word
  I2C1_FIFOCFG.B.TXBS = 0;     // Burst size 1 word
 
  clearWdtEndinit();
  
  /* Configure PORT settings for I2C_1 SDA/SCL pins*/
  P11_IOCR12.B.PC14 = 0x00;         // SCL input -> P11.14
  P11_IOCR12.B.PC13 = 0x00;         // SDA input -> P11.13
  I2C1_GPCTL.B.PISEL = 0x00;        // PORT-A selected
  
  setWdtEndinit();
  
  /* Enable I2C1 module */
  I2C1_RUNCTRL.B.RUN = 1;      // I2C1 Module enabled - configuration 
                               // registers not accessible

 

Before Master write sequence, both error and protocol interrupt sources are enabled. Then the packet size is writen to TPSCTRL register and the packet data is writen to TXD register. After that, Master waits until TX_END request is set by PIRQSS register. After that, write sequence ends.

Also during this sequence, after TXD register is being written to, following status is set:  I2C0_BUSSTAT.BS = 2 (busy master), I2C1_BUSSTAT.BS = 1 (bus busy). Also, after address being send, I2C1_BUSSTAT.BS = 1 (bus busy) but I2C1_BUSSTAT.RnW = 0 (device is transmitting - although it should equal to "1" as it Slave and is being addressed).

Is there anything that might have to be reconfigured otherwise or not configured here but should be? Should additional steps be taken at Slave side during Master write sequence?

 

Show Less

Hi all,

Why is the parameter Data Flash erase disturb limit defined in the datasheet and where comes the value 50 from?


Thanks and best regards

Lucas



#8042000 12021 Show Less

I wanted to make sure I'm working correctly.

I have 1 ISR (isr_can - see in attached layout) to handle both new Rx message and CAN off state.

1. Is this the correct method to check if CAN is in off state: if (CAN_INT_SR_REG & CAN_BUS_OFF_MASK) ?
   in a more general way, how can I tell the interrupt source?
2. How do I clear the interrupt flag of can bus off mask? (to clear receive message flag I do this : CAN_INT_SR_REG = CAN_RX_MESSAGE_MASK)

Show Less

Hi,

 

using the XMC Library (newest version) with a compiler with -std=c++20 flag set results in many warnings like this: compound assignment with 'volatile'-qualified left operand is deprecated. And as there are many |= and &= in this low level code, this produces a huge amount of warnings.

As those expressions are not only in the source files but also in inline functions in the header files, building the XMC library as static library under C++17 is also not a solution to this problem.

As these compound operations with 'volatile'-qualified left operands will probably do not come back in future standards it would be great if you could come up with a solution to this.

A possibility would be this one. It produces the exact same assembly output if -O0 is not set.

What is your view on that?

 

Yours,

Elias

Show Less

My dev-board is installed KitProg2 by default.

I want to update the firmware from KitProg2 to KitProg3.

Can I back-up default sipped state before update it by PSoC Programmer.

If I can't, could you tell me how to return from updated state to sipped state.

Thank you.

Show Less

I'm trying to automate the programming of a CY8C3445AXI-104 device using the ppcli application, the problem I have is that I cannot find the ppcli command that will write the data to the PSoC from a hex file that has been read in. The following lines of code appear to work, but I'm at a loss as to what commands are used to program and verify the Hex file.

OpenPort MiniProg3/1636BB000190 .
HEX_ReadFile "C:\\PSOC_CLI_Programmer\\Application\\2001HPC_V_21_for_CY8C3445AXI-108.hex"
SetAcquireMode “Reset”
SetProtocol 1
SetProtocolClock 152
SetPowerVoltage 3.3
DAP_Acquire
PSoC3_EraseAll

I assume that the commands would be "PSoC3_ProgramRowFromHex" and "PSoC3_VerifyRowFromHex", but need further information on how to use these commands.

Am I also correct in thinking that the script would be completed with the following:

PSoC3_ProtectAll
PSoC3_VerifyProtect
DAP_ReleaseChip
ClosePort
Quit

 

Show Less