Part Number: AM4372

Hello dear e2e-Team,

which configurations do I have to do on my Host-PC that the ROM-Bootloader will boot the uboot-files over Ethernet? Do you have any Manuals for this?

Thanks!

m.u. 

Part Number: CC2652R

Hello, is it true that in the chip CC2652R "256kb of ROM for protocols and library functions" is used to write TI-RTOS kernel and low-level drivers? 

Is it true that "352KB  of in-system Programmable Flash" is allocated only for user programs?

Part Number: CC3220SF

Hello!

My custom CC3220SF board unexpectedly reboots every 10-300 seconds. 

PRCMSysResetCauseGet() returns PRCM_POWER_ON.

I've checked VCC 3.3V line and Reset line using oscilloscope, they has constant 3.3V value on the reset event.

That else can cause PRCM_POWER_ON reset?

Part Number: DS25BR440

Hi Team,

Do we have DS25BR440 IBIS or PSPICE model? If so, could you please send to me? Thanks!

Best Regards!

Hao

Part Number: TMS320F28377D

Hi,

You are my last hope, been pulling my hair out for last couple of weeks. Got 6 brand new boards built with TMS320F28377D on them, 2 - work, 4 don't. Replaced MCU on one of the boards that did not work - still does not work. Got some very expensive software to rule out JTAG issues - JTAG is fine. Power supplies are fine. +3V3, +1V2 are fine. Grounding is fine. No shorts detected. Nothing is warming up that should not. I can control IOs via the JTAG software.

So down the rabbit hole I go.

1. Set Boot mode pins (GPIO72,GPIO84) to 1,0 respectively to get the MCU into WAIT mode and try to flash the firmware. Output I get is 

C28xx_CPU1: GEL Output: 
Memory Map Initialization Complete
C28xx_CPU1: If erase/program (E/P) operation is being done on one core, the other core should not execute from shared-RAM (SR) as they are used for the E/P code. Also, CPU1 will be halted to determine SR ownership for the CPU which will run the Flash Plugin code, after which CPU1 will be set to run its application. User code execution from SR could commence after both flash banks are programmed.
C28xx_CPU1: Writing Flash @ Address 0x00080000 of Length 0x00000008 (page 0)
C28xx_CPU1: Error: (Error -1135 @ 0xC095) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 8.2.0.00004) 
C28xx_CPU1: Trouble Halting Target CPU: (Error -1044 @ 0x0) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 8.2.0.00004) 
C28xx_CPU1: Error: (Error -1135 @ 0xC095) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 8.2.0.00004) 
C28xx_CPU1: Unable to determine target status after 20 attempts
C28xx_CPU1: Failed to remove the debug state from the target before disconnecting.  There may still be breakpoint op-codes embedded in program memory.  It is recommended that you reset the emulator before you connect and reload your program before you continue debugging
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0007026D@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F444@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x00130@Program: target is not connected
C28xx_CPU1: PLL configuration status = 0.
C28xx_CPU1: Error executing PLL configuration algorithm. Operation cancelled. (0x0)
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D200@Data: target is not connected
C28xx_CPU1: File Loader: Memory write failed: Unknown error
C28xx_CPU1: GEL: File: C:\ProjectFiles\rimac\obc\src\clp\obc\ccs\OBC_A_Debug\obc.out: Load failed.
C28xx_CPU1: Error occurred during flash operation: Could not read register PC: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F800@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x00000@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Cannot enable while the target is disconnected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0007026D@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F444@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Failed to run target while trying to execute pwrite_en.alg
C28xx_CPU1: Flash operation timed out waiting for the algorithm to complete. Operation cancelled.
C28xx_CPU1: Perform a debugger reset and execute the Boot-ROM code (click on the RESUME button in CCS debug window) before erasing/loading the Flash.  If that does not help to perform a successful Flash erase/load, check the Reset cause (RESC) register, NMI shadow flag (NMISHDFLG) register and the Boot-ROM status register for further debug.
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0007026D@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F444@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0007026D@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D200@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x5D200@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0007026D@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D20E@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D20E@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D20E@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D20E@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D22E@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D208@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D208@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D208@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D208@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D222@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D222@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D214@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D20E@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D20E@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D20E@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D222@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D200@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x00000@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Cannot enable while the target is disconnected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0007026D@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F444@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Failed to run target while trying to execute pwrite_dis.alg
C28xx_CPU1: Flash operation timed out waiting for the algorithm to complete. Operation cancelled.
C28xx_CPU1: Perform a debugger reset and execute the Boot-ROM code (click on the RESUME button in CCS debug window) before erasing/loading the Flash.  If that does not help to perform a successful Flash erase/load, check the Reset cause (RESC) register, NMI shadow flag (NMISHDFLG) register and the Boot-ROM status register for further debug.
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0007026D@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F444@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write register PC: target is not connected

At no point power supplies trip or go low - very unsure as to why the target it not connected.

2. Instead of flashing code, connecting to the MCU via debugger to see what is happening inside (Using the same .ccxml as the Debug Configuration).

I Launched the .ccxml from the Target Configurations in CSS and Connected to the CPU 1 core. Great. Do System Reset then CPU Reset.

Looking at the Disassembly tab, I can see that the Program Counter is at 0x003FF16A. Looking at the Delfino user manual, it seems that this is somewhere within the Secure ROM area.

I let the code execute and it gets itself into ESTOP0, the Program Counter is at 0x003FE2ED which is within the Boot ROM space. The MemoryErrRegs, RomWaitStateRegs and RomPrefetchRegs registers are all 0s.

RESC register shows that XRSn and TRSTn are 1, everything else is 0.

I am using Blackhawk USB560-v2 Debugger, but I tried XDS200 too and it is the same issue.

3. Return Boot Mode pins both to HIGH, so the Boot ROM jumps to Boot from Flash instead of Wait.

Again, Launch Target Configuration connecting to the target, System Reset, CPU Reset, let the code to execute, it stops at ITRAP0 @0x0 from 0x0F189 (GS3 RAM)?

So, what is going on here? I am lost. Any advise on what I am doing wrong, what could be causing what I am seeing would be much appreciated. I can flash the same code with the exact same tools on the other 2 boards and they work, but these 4 are just dead.

Much appreciated

Part Number: TMDSEMU110-U

Hi,

I am trying to control the XDS110 GPIOOUT pins in a custom embedded XDS110 design. In a related thread https://e2e.ti.com/support/microcontrollers/other/f/908/p/824023/3049028#3049028 I got the info that the logical GPIOOUT0 pin maps to PF0 on the Tiva MCU.

On the PC I am running this batch file to toggle GPIOOUT0..1 on and off:

:loop
dbgjtag.exe -f @xds110 -Y gpiopins,config=0x3,write=0x3
dbgjtag.exe -f @xds110 -Y gpiopins,config=0x3,write=0x0
goto loop

As a first test, I connect the original TMDSEMU110-U with the little AUX breakout board and apply 3.3V to TGTVDD(SENSE). I can see a square wave on GPIOOUT0 and GPIOOUT1 using an oscilloscope - as expected.

To try the same on custom hardware, I am using an EK-TM4C1294XL launchpad. I installed a 16 MHz crystal and flashed the XDS110 firmware. The board correctly shows up as XDS110 on the PC and the xdsdfu and dbgjtag tools will talk to it without a problem.

Running the batch scripts now, I see no activity on any of the PF0..3 pins, they all sit at 0V.

Reading back the GPIO config after running the batch file always returns 0 (on the TMDSEMU110, I see the config value 0x03 as set from batch file):

dbgjtag.exe -f @xds110 -Y gpiopins -v

-----[Print the board config pathname(s)]------------------------------------

xds110.i

-----[Print the controller-open software log-file]---------------------------

The library build date was 'Jan 24 2019'.
The library build time was '14:27:46'.
The library package version is '8.0.903.6'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '5' (0x00000005).
The controller has an insertion length of '0' (0x00000000).
The user GPIO pin config is 0x00.
The user GPIO pin input is  0x00.

What am I doing wrong? Do the version pins PK4..7 need to be set to a specific value? Is there some other connection that I need to make to get the GPIOs to function?

Thanks for your help

Part Number: BQ34Z100-G1

I have made a battery with 8 cells NIMH.

I have calibrated it 

Voltage and curent from BQtudio is OK.

When I charge and discharge the capacity is not OK (always the same)

What do you think about it?

Best regars JCD

PS I send you 3 meesage for this problem but I 've never received an answer.

We have a question about UCC28180.

We can find the information of VREF at Ta=25℃ in datasheet p.6.

Please tell us the 3σ and 4σ of Vref at Ta=25℃.

Best regards,

Takahiro Nishizawa

Part Number: TMS320F28377S

Tool/software: Code Composer Studio

Hi all,

Trying to connect target TMS320F28377s using JTAG XDS100 v2 debugger unable connect the target and console shows the error below

The CCS was recently  installed on windows 7and when we try to load program or debug, After compilation JTAG tries to connect  target but it fails and console displays following error. This is the 

C28xx_CPU1: GEL: Error while executing OnTargetConnect(): identifier not found: ST1
     at ST1=(ST1&~(0x0100)) [f28377s.gel:307]
     at C28x_Mode() [f28377s.gel:89]
     at OnTargetConnect()
C28xx_CPU1: GEL: Error while executing OnReset(0): identifier not found: XAR0
     at XAR0=*((unsigned long *) 0x703F0) [f28377s.gel:403]
     at SetupDCSM() [f28377s.gel:32]
     at OnReset(0)
C28xx_CPU1: GEL: Error while executing OnReset(0): identifier not found: XAR0
     at XAR0=*((unsigned long *) 0x703F0) [f28377s.gel:403]
     at SetupDCSM() [f28377s.gel:32]
     at OnReset(0)
C28xx_CPU1: GEL: Error while executing OnRestart( 0 ): identifier not found: ST1
     at ST1=(ST1&~(0x0100)) [f28377s.gel:307]
     at C28x_Mode() [f28377s.gel:59]
     at OnRestart(0)
C28xx_CPU1: Trouble Setting Breakpoint with the Action "Finish Auto Run" at 0x900b0: (Error -1066 @ 0x900B0) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 8.0.27.9)
C28xx_CPU1: Breakpoint Manager: Retrying with a AET breakpoint
C28xx_CPU1: Breakpoint Manager: Error enabling this function: Failed to retrieve ID for DCU_SEL.

 first time we are facing the problem. Please suggest.

Regards

Naveen

Part Number: BOOSTXL-SENSORS

Hi,

I'm running the BOOSTXL-SENSORS BoosterPack on the MSP432P401R LaunchPad. In the Users Guide Section 3.2 It says that there is a TI-RTOS example of the source code called "BOOSTXL-SENSORS_TI-RTOS_SensorGUI_MSP432P401R to be found in the SimpleLink MSP432 SDK. I can find the "No RTOS" version but cannot find the TI-RTOS version mentioned in the SimpleLink MSP432 SDK and I want to run this example as my I want to use the TI-RTOS version.

Please can someone tell me where to look or send a link to this example so I can import it into CCS.

Many Thanks,

Bill

Part Number: TMS320F28379D

Tool/software: Code Composer Studio

Hi

How to fix these errors?

Part Number: SN65DSI85-Q1

Dear team,

The oscilloscope measurement is used to find that the DSI85 input signal is normal, but one of the output terminals has no video signal output while has the backlight.

At this time, read CSR 0xE5 and CSR 0xE6, their value are all 0x00 which means no error detected.

In addition, the power on sequence is as below, is there any problem about it?

Thanks & Best Regards,

Sherry

Part Number: TMS320F28388D

Hi,

Chapter 3.7.3.3 of the F28388 TRM (SPRUII0) states that "the ePWM clockl each have an additional /2 divider, which is required to support CPU frequencies over 100MHz". However the datasheet states that the ePWM and HRPWM work with frequencies up to 200MHz. 

Can someone confirm that the ePWM modules do work up to 200MHz?

Thanks,

Pierre

Part Number: DAC80504

We are planning to use DAC80504 in our application.  we would want to give reference of 5V to REF pin.  Our VDD is +5V.   Datasheet says Reference input range can be equal to VDD if REFDIV is enabled.  If we enable REFDIV(i.e, REFDIV=1), and Gain = 1, VOUT can be in range of 0-Vref.  Does that mean Vout is 0-5V ?

As per our understanding we can give 5V external reference , then we will set REFDIV=1, GAIN=1 to get Output voltage range 0 to 5V.  Please confirm.

Awaiting for the quick response.

Part Number: CC3120

Hi team,

Could you please simplify the programming flash produce once my CC3120 on my PCB and I would like to program the serial flash.

I am familiar with http://www.ti.com/lit/an/swra569/swra569.pdf app note.

but it not clear which tool we need to use to programming the flash, can you please elaborate more about the SPI programmer (which kind tool is it and where to get it).

What TI recommends in order to program the serial flash?

Thanks in advance and regards,

Shai

Part Number: DAC8775

Hi team,

I want to use dac8875 with spi to genrerate current that is range between 0-20mA. Which order that includes address and data does ideal to generate current?

Example

1-0x03 address  - 0x0101 data (select 0-20mA)

2-0x05 address - 0x9999 data (generate 12mA)

Regards,

Emre Özçelik

Part Number: CC8520

Dear TI expert,

We are developing a wireless microphone product based on TI wireless headset reference design which is built on CC8520+CC2592 respectively. The solution has managed to achieve a communication distance over 30M in open area environment. However, we noticed that range performance drops  significantly to about 5 meter under moderate interference where both WIFI and Bluetooth exist within the testing environment. The wireless headset product is configured to operate at standalone mode - no host MCU is attached to CC8520. Could you please advise if there is any system parameters which I can play with in order to enhance the communication range?

Best regards,

Peter     

Part Number: CC2640R2F

Tool/software: Code Composer Studio

Hello,

I have started working on bidirectional audio transfer, I am using cc2640r2f(5x5), I want to transfer audio from mobile device to peripheral device and visa-versa,

could you suggest what example I should refer for this and which hardware I should use for audio codec?

regards,

Jaydipsinh

Part Number: AWR1843

We want to use TX phase shift on AWR1843. In the picture attached is a part of rl_sensor.h from mmwave SDK 03_02_00_04.

It says that phase shift value for all TX antennas is 8bit data. Is it signed or unsigned value? I suppose phase shift goes from -90 to 90 possibly.

I understand you used it for AWR1243P but it says that can be used for AWR1843 with txPhaseShifter field in profile Config.

As it is described in document: http://www.ti.com/lit/ug/tiduen5/tiduen5.pdf Imaging Radar Using Cascaded mmWave Sensor Reference Design (pages 12/13)

it says that when 2*lambda is between TX antennas, we have 0, 4pi*sin(theta), 8pi*sin(theta),... and that is clear. But is not clear for example how 32*pi*sin(theta) will be written into 8bit register.

( Unless you subtract n*360 ? )

TX0:  0 is written in register of first TX antenna.

TX1:  4pi*sin(theta) and theta = 30deg in register we need to write: integer(4pi*sin(30) * 180/pi / 5.625 = 64), 64 is written in register of second TX antenna?

TX2:  8pi*sin(theta) and theta = 30deg in register we need to write: integer(8pi*sin(60) * 180/pi / 5.625 = 221), 221 is written in register of third TX antenna?

What about negative angle for beam steering? If we want for example -45 degrees, 4pi*sin(theta) and 8pi*sin(theta) are negative, what to do then?

Short explanation about data formats should be a good answer to the question.

Regards,

Predrag

Part Number: DP83848J

Hi:

our product USES TI DP83848NRATR, the main platform RK3288 plus DP83848NRATR.During Ethernet use, the machine automatically disconnects and reconnects for many times, and eth0 switches down up several times in a day. In theory, the updateInterface will only be triggered by plug and unplug state or boot detection Below is our schematic diagram, please give some Suggestions, thank you!