Part Number: TPS2660
Dear Forum,
I know this issue has been slightly covered before, but unfortunately there hasn't been any good answer to this.
I don't wanna use a MCU with the TPS2660x, therefore I'dont have a use for the SHDN pin. Cn I leave it floating? has the device an internal pullup in oder to enable it? If not, what would be the reccomended way to enanble the device if varying input voltages may occur?
Best and many thakns,
A.
Tool/software: Code Composer Studio
Downloaded CCS http://www.ti.com/tool/CCSTUDIO V9
Is it now free? or need to purhcase for CC1310
If not free, what is code size/time limited options in free version
Part Number: TIDA-01093
Dear All,
I am working TIDA-01093, In that I have replace DC-Dc part LM25018MR with URB4805MT 3WR3.
because of this replacement what will be effect on Q21 current consumption?
and is this current consumption is acceptable for URB4805MT 3WR3?
waiting for earliest reply,
Best regards,
Prathamesh
Part Number: TM4C1294NCPDT
Tool/software: TI C/C++ Compiler
Hi,
I have getting this linking error while compiling my project.
<Linking>
"configPkg/linker.cmd", line 155: warning #10096-D: specified address lies outside memory map
error #10264: DEFAULT memory range overlaps existing memory range FLASH
error #10264: DEFAULT memory range overlaps existing memory range SRAM
error #10010: errors encountered during linking; "gluon-target-wifi.out" not built
>> Compilation failure
makefile:228: recipe for target 'gluon-target-wifi.out' failed
gmake: *** [gluon-target-wifi.out] Error 1
gmake: Target 'all' not remade because of errors.
**** Build Finished ****
Please let me know what are these and how to fix. I am using ti rtos with ccs
Part Number: MSP430FR5872
Hi,
I am using the MSP430FR5872 part on my custom board. It supports a "test watchdog" command via CLI (UART) that puts the firmware into a infinite loop to verify the watchdog functionality.
Here is the sequence used:
1) Board powered up and CLI command issued to test watchdog to put FW in infinite loop
2) As expected few seconds later the watchdog reset occurs and the interrupt vector register (SYSRSTIV) shows the interrupt event as WDTIFG watchdog time-out (PUC) 0x16 on rebooting. We store the value of SYSRSTIV in a local variable in the first instruction in the main() before the watchdog is initialized or started to prevent any possible changes to it.
3) After rebooting from step 1 we repeat the command to "test watcdog" once more.
4) Few seconds later the watchdog reset occurs and the interrupt vector register (SYSRSTIV) shows the interrupt event as RSTIFG RST/NMI (BOR) 0x4. The interrupt vector should have shown 0x16 as in step 2. This issue is repeatable.
Can the SYSRSTIV register have both WDTIFG and RSTIFG flags set at the same time ?
The firmware needs to perform certain operations based on the last reset cause and its vital to identify the WDT reset event !
Any suggestions/help would be greatly appreciated. Thanks !
Regards,
Aman
Part Number: CC1310
Tool/software: Code Composer Studio
I need to work on TI-RTOS for CC1310. But in resource explore i couldn't find "TI RTOS for simplelink",
"TI RTOS for Tiva " is available?
I have "simplelink_cc13x0_sdk_3_20_00_23" though installed, does that include RTOS for CC1310 or it is differnet?
Part Number: AM3352
did no find am335x_evm_nor_config / am335x_evm_norboot_config under u-boot-2019.01.
How to build UBOOT-2019.01 to support NOR boot.
Part Number: TLV320AIC3105
Dear all
I'm using TLV320AIC3105 in my product and I noticed the following :
When Left/Right-ADC PGA Gain Control Registers (reg 15 and 16) programmed value are higher than about 50 (7bits), the ADC stops recording.
I suppose an overflow condition occurs at that time.
Reducing gain allows to make the ADC working again.
Is this the expected behavior ?
If so, what would be the workaround to allow the ADC working even if an overflow occurred ? I do not want to have to read periodically overflow registers.
Those gain registers are accepting 7bits gain from 0 to 127, and I cannot program the full 7bits range due to the above issue.
Any help would be greatly appreciated.
Thanks
Jerome
Part Number: MSP432P401R
I am using the MSP432 Launchpad and the Sensor BoosterPack with FreeRTOS. I establish a I2C connection between the MSP432 and the OPT3001, I then want to give this data to the CC2650 however it seems that the CC2650 can only use TI-RTOS.
Is it possible to implement a I2C connection between a device using TI-RTOS and a device using FreeRTOS in the same project? Or would I have to switch to using TI-RTOS for all the hardware I am using?
Also, are the TI-RTOS drivers for the cc2650 usable in FreeRTOS?
Part Number: LMV321A
Hi sirs,
Is LMV321AIDCKR p-p compatible with LMV321IDCKR?
What's the difference and advantage for A-version?
Thanks a lot!
Best Regards,
Sean Liao
Part Number: TPS2412
Hi TI and other experts.
For a new server design we would like to incorporation a redundant power scheme constructed by two independent power supplies (instead of a ready made one). This is to make is possible to monitor what is going on. For that we need an Oring concept. It is a 12V system. 20A on each supply. Hence a total of 40A.
It has to be realized such that one supply can fail short and the other will still operate. It also has to be realized (if possible) such that load sharing is a natural part of the system. Each supply will deliver about half of the power in normal operation.
What solution(s) should we consider. TPS2412? There might be other that are better suited for a 12V "high current" system.
Thanks in advance.
Best, Christian
Part Number: CC1350STK
Tool/software: Code Composer Studio
Hi, I was wondoring if any of you guys had som advice regarding modification of the TIDA01469-Firmware to work on the CC1350 SensorTag?
Part Number: AM3358
We have a design with am3358 and emmc. The system is based on processor-sdk-linux-02.00.02.
During the long-time test, about two months later, we found that some boards worked abnormally with emmc. Do you have any advice to fix this issue.
The log is shown below:
arm login: [ 118.704259] mmcblk0: error -110 transferring data, sector 6946619, nr 24, cmd response 0x900, card status 0xc00
[ 118.714895] mmc1: tried to reset card
[ 118.720446] blk_update_request: I/O error, dev mmcblk0, sector 6946619
[ 118.728626] blk_update_request: I/O error, dev mmcblk0, sector 6946627
[ 118.736570] blk_update_request: I/O error, dev mmcblk0, sector 6946635
[ 118.765374] Aborting journal on device mmcblk0p3-8.
[ 128.331266] EXT4-fs error (device mmcblk0p3): ext4_journal_check_start:56: Detected aborted journal
[ 128.349521] EXT4-fs (mmcblk0p3): Remounting filesystem read-only
[ 131.710798] mmcblk0: error -110 transferring data, sector 14732640, nr 16, cmd response 0x900, card status 0xc00
[ 131.721509] mmc1: tried to reset card
[ 131.725334] blk_update_request: I/O error, dev mmcblk0, sector 14732640
[ 131.734100] blk_update_request: I/O error, dev mmcblk0, sector 14732648
[ 131.741432] EXT4-fs warning (device mmcblk0p4): ext4_end_bio:332: I/O error -5 writing to inode 42 (offset 1757184 size 4096 starting block 1841582)
[ 131.755669] Buffer I/O error on device mmcblk0p4, logical block 132524
[ 131.762784] Buffer I/O error on device mmcblk0p4, logical block 132525
[ 135.859692] mmcblk0: error -110 sending status command, retrying
[ 135.866005] mmcblk0: timed out sending r/w cmd command, card status 0xe00
[ 135.900569] mmcblk0: timed out sending r/w cmd command, card status 0x400e00
[ 135.960153] mmcblk0: timed out sending r/w cmd command, card status 0x400e00
[ 135.993663] mmcblk0: timed out sending r/w cmd command, card status 0x400e00
[ 136.027331] mmcblk0: timed out sending r/w cmd command, card status 0x400e00
[ 136.060954] mmcblk0: timed out sending r/w cmd command, card status 0x400e00
[ 136.068416] mmc1: tried to reset card
[ 136.072248] blk_update_request: I/O error, dev mmcblk0, sector 13672448
[ 136.079865] Buffer I/O error on dev mmcblk0p4, logical block 0, lost async page write
[ 136.088400] blk_update_request: I/O error, dev mmcblk0, sector 13672456
[ 136.095318] Buffer I/O error on dev mmcblk0p4, logical block 1, lost async page write
[ 136.156437] mmcblk0: timed out sending r/w cmd command, card status 0x400e00
[ 136.216050] mmcblk0: timed out sending r/w cmd command, card status 0x400e00
[ 136.275731] mmcblk0: timed out sending r/w cmd command, card status 0x400e00
[ 136.309842] mmcblk0: timed out sending r/w cmd command, card status 0x400e00
[ 136.369309] mmcblk0: timed out sending r/w cmd command, card status 0x400e00
[ 136.429068] mmcblk0: timed out sending r/w cmd command, card status 0x400e00
[ 136.436622] mmc1: tried to reset card
[ 136.440959] blk_update_request: I/O error, dev mmcblk0, sector 13954392
[ 136.448163] blk_update_request: I/O error, dev mmcblk0, sector 13954400
[ 136.455101] blk_update_request: I/O error, dev mmcblk0, sector 13954408
[ 136.462440] blk_update_request: I/O error, dev mmcblk0, sector 13954416
[ 136.469667] blk_update_request: I/O error, dev mmcblk0, sector 13954424
[ 136.529074] mmcblk0: timed out sending r/w cmd command, card status 0x400e00
[ 136.588784] mmcblk0: timed out sending r/w cmd command, card status 0x400e00
[ 136.648247] mmcblk0: timed out sending r/w cmd command, card status 0x400e00
[ 136.707856] mmcblk0: timed out sending r/w cmd command, card status 0x400e00
[ 136.768072] mmcblk0: timed out sending r/w cmd command, card status 0x400e00
[ 136.827867] mmcblk0: timed out sending r/w cmd command, card status 0x400e00
[ 136.835248] blk_update_request: I/O error, dev mmcblk0, sector 5615835
[ 136.842683] blk_update_request: I/O error, dev mmcblk0, sector 5615843
[ 136.849891] blk_update_request: I/O error, dev mmcblk0, sector 5615851
[ 136.856751] blk_update_request: I/O error, dev mmcblk0, sector 5615859
[ 136.864038] blk_update_request: I/O error, dev mmcblk0, sector 5615867
[ 136.871138] blk_update_request: I/O error, dev mmcblk0, sector 5615875
[ 136.878236] blk_update_request: I/O error, dev mmcblk0, sector 5615883
[ 136.885064] blk_update_request: I/O error, dev mmcblk0, sector 5615891
[ 136.892332] blk_update_request: I/O error, dev mmcblk0, sector 5615899
[ 136.900725] blk_update_request: I/O error, dev mmcblk0, sector 5615907
[ 137.140771] mmcblk0: timed out sending r/w cmd command, card status 0x400e00
[ 137.174461] mmcblk0: timed out sending r/w cmd command, card status 0x400e00
[ 137.233599] mmcblk0: timed out sending r/w cmd command, card status 0x400e00
[ 137.293112] mmcblk0: timed out sending r/w cmd command, card status 0x400e00
[ 137.352467] mmcblk0: timed out sending r/w cmd command, card status 0x400e00
[ 137.411567] mmcblk0: timed out sending r/w cmd command, card status 0x400900
[ 137.418973] Buffer I/O error on dev mmcblk0p4, logical block 51, lost async page write
[ 139.316849] mmcblk0: error -110 transferring data, sector 13672880, nr 8, cmd response 0x900, card status 0xc00
[ 139.327460] Buffer I/O error on dev mmcblk0p4, logical block 54, lost async page write
Part Number: HDC2080
Hi Team,
Is it possible to connect ADDR to VDD or GND directly? Or Is it better to pus a couple of kohm resister between ADDR to VDD or GND?
Regards,
Takashi Onawa
Part Number: IWR1642BOOST
Tool/software: Code Composer Studio
Hi guys,
I am trying to build a project that predicts the direction of movement of user with IWR1642BOOST but I don't know where to start with this. I can see there are mss and dss coding files but I want to know more like how to build up these files to run this project, and what are the following steps to build this project. If you have any ideas on how to start working on this in details, please help me.
Thank you!
Part Number: TPS22976
Hello,
just for my understanding: Quiescent Current in the datasheet is the current that flows when one or both inputs are switched on the output and shutdown current is the current that flows when both inputs are not selected and the output voltage is 0 volts.
Is this right?
Thank you very much!
Part Number: TXS0102
Hi,
What is happening with VCCA side if VCCB is OFF (not present) ? I assume that the I2C bus is still working for I2C devices on VCCA side, and not get stucked.
What is happening with VCCB side if VCCA is OFF (not present) ? I assume that the I2C bus is still working for I2C devices on VCCB side, and not get stucked.
Reference first picture in data sheet
Kind regards
Jorgen
Part Number: AM5728
1.LINUX-RT : ti-processor-sdk-linux-rt-am57xx-evm-06.00.00.07-Linux-x86-Install
RTOS:ti-processor-sdk-rtos-am57xx-evm-06.00.00.07-Linux-x86-Install
2.When I build the IPC
make ti-ipc
cd /home/jailhouse/ti/ipc_3_50_03_05; \
./configure ${CONFIGURE_FLAGS} \
CC=${CC} \
--prefix=/usr \
PLATFORM=DRA7XX \
KERNEL_INSTALL_DIR=/home/jailhouse/ti-processor-sdk-linux-rt-am57xx-evm-06.00.00.07/board-support/linux-rt-4.19.38+gitAUTOINC+1224cd679e-g1224cd679e
/bin/sh: 51: export: --sysroot: bad variable name
Makefile:800: recipe for target 'ti-ipc-linux-config' failed
make: *** [ti-ipc-linux-config] Error 2
What should I do?
3. I Compared the code about environment-setup and Rules.mak between 0403 and 0600
there is no sysroot in 0403
so I remove the sysroot in 0600, and I can build the ti-ipc
WHY?
