CC3200: Does sl_Stop clear all configurations stored on the network processor?

May 9, 2017, 3:40 am

≫ Next: CC3200: Getting the gpio pin wake up source

≪ Previous: WEBENCH® Tools/UCC28070: controller design

Part Number:CC3200

Hi,

I have a question regarding the network processor:

1. In the ConfigureSimpleLinkToDefault State() function, first the cc3200 is set to Station mode. Then a lot of configurations are done including policies, etc. At the end of this function sl_Stop() is called.

When sl_Stop() is called the Network processor is reset so all the previous settings are deleted. So what is the reason sl_Stop() is called at the end ot this function.

Can someone please clarify?

thanks and regards,

Rajkumar

↧

CC3200: Getting the gpio pin wake up source

May 9, 2017, 3:50 am

≫ Next: AFE5809EVM: AFE5809EVM Digital Demodulator

≪ Previous: CC3200: Does sl_Stop clear all configurations stored on the network processor?

Part Number:CC3200

Hello,

How can i identify the Gpio pin Wakeup source when the cc3200 exit the LPDS?
I want to know exactly the Pin number.

Thank you.

↧

AFE5809EVM: AFE5809EVM Digital Demodulator

May 9, 2017, 3:55 am

≫ Next: Uniflash - formatting with wrong capacity

≪ Previous: CC3200: Getting the gpio pin wake up source

Part Number:AFE5809EVM

Hello,

I am trying to use AFE5809EVM Demodulator feature.

1. If possible, Can you guys please help me to design filter for 40/32 = 1.25 MHz ?

2. If possible I would like to set filter cut-off freq to 350 KHz.

Please let me know if you need any further information.

Thank you.

↧

Uniflash - formatting with wrong capacity

May 9, 2017, 4:02 am

≫ Next: report attribute failed issue

≪ Previous: AFE5809EVM: AFE5809EVM Digital Demodulator

We are using uniflash to program CC3200 devices.

If I understand the guide correctly, it should be formatted to 1MB.

Unfortunately we've accidentally formatted some of our early devices with 8MB.

So my questions are:

1. Could this really cause problems?

2. Is it possible this will lead to failure in creating file even thought there is enough space on the flash?

3. Does formatting again, this time to 1MB fix any problems which might have been caused by the first "wrong formatting"?

Thanks in advance!

Tal

↧

report attribute failed issue

May 9, 2017, 4:04 am

≫ Next: LM5060-Q1: Disable UVLO

≪ Previous: Uniflash - formatting with wrong capacity

hi all,

have anyone give me a Suggest for it ?

sometime it don't send out when i report attribute .

i create a Period timer(5s) to send report ,every timeout handle it increase variable(ButCD) and caller send report(Switch_sendToggle)

it seem it do't update attribute information immediately.

static void Switch_sendToggle(void)
{
    afAddrType_t dstAddr;
    zclReportCmd_t *pReportCmd;

    // Build and send a ZCL temperature reading to the matched device
    pReportCmd = ICall_malloc(sizeof(zclReportCmd_t) + sizeof(zclReport_t));
    if(pReportCmd != NULL)
    {
        dstAddr.addrMode = (afAddrMode_t)zswDstAddr.addrMode;
        dstAddr.addr.shortAddr = zswDstAddr.addr.shortAddr;
        dstAddr.endPoint = zswDstAddr.endpoint;
        dstAddr.panId = zswDstAddr.panID;
        pReportCmd->numAttr = 1;
        pReportCmd->attrList[0].attrID = ATTRID_BUTTON_CD;
        pReportCmd->attrList[0].dataType = ZCL_DATATYPE_UINT8;
        pReportCmd->attrList[0].attrData = (void *) (&ButCD);
        // Call ZCL function to send the report
        zcl_SendReportCmd(SWITCH_EP, &dstAddr,
                ZCL_CLUSTER_ID_AMIGO, pReportCmd,
                ZCL_FRAME_SERVER_CLIENT_DIR, true, swTransID++);

        ICall_free(pReportCmd);
    }
}

↧

LM5060-Q1: Disable UVLO

May 9, 2017, 4:13 am

≫ Next: TSW1400EVM: AFE5809 + TSW1400 - not working

≪ Previous: report attribute failed issue

Part Number:LM5060-Q1

Hello,

Can we use the UVLO of the LM5060-Q1 as Disable? (Pull up to VIN)
Vin may drop to about 3V.
However, there is LM5122 - Q1 at the back of LM5060 - Q1, and 10V of boosted output is applied at LM5122 - Q1 after start - up.

Best Regards,
Ryuji

↧

TSW1400EVM: AFE5809 + TSW1400 - not working

May 9, 2017, 4:14 am

≫ Next: LM3447-PAR-230VEVM: does not work truly

≪ Previous: LM5060-Q1: Disable UVLO

Part Number:TSW1400EVM

Hi,

We are using AFE5809EVM and TSW1400 to run some tests but TSW1400 doesn't seem to work at all. There is no LED light turning on. But in the GUI it shows connected. Also, JTAG_CHAIN_ERROR is popping up.

I have used these boards few months ago and was able to manage to get rid of JTAG CHAIN ERROR but now, it is strange that none of the LED is on.

What would be causing an issue? We want to simulate I/Q data at the moment.

Thank you!

↧

LM3447-PAR-230VEVM: does not work truly

May 9, 2017, 4:21 am

≫ Next: OPT8241-CDK-EVM: obsolete parts.

≪ Previous: TSW1400EVM: AFE5809 + TSW1400 - not working

Part Number:LM3447-PAR-230VEVM

I have bought LM3447-PAR-230VEVM.
In the datasheet,

www.ti.com/.../sluua02.pdf

page 11, fig12, you show input current.
But I have not obtained this current,
The input voltage and current graph is in the following link:

www.yunusuzun.com/SCR01.BMP

What is the problem?
My board is broken? or?

Best regards

↧

OPT8241-CDK-EVM: obsolete parts.

May 9, 2017, 4:25 am

≫ Next: Linux/SN65DSI83: generates test pattern OK, but fails to streaming MIPI DSI data

≪ Previous: LM3447-PAR-230VEVM: does not work truly

Part Number:OPT8241-CDK-EVM

Hi,

in the BOM in the file name BOM_OPT8241-CDK-EVM SB REV2P0V1.xls U7: MT47H32M16HR-25E-G_0

However, this part is obsolete according to digikey[1] , and it can not be found in Micron's website. I assume it has been replaced by another one. Can you please guide me to which part was used as a replacement for it.

Best Regards,

Moetaz

↧

Linux/SN65DSI83: generates test pattern OK, but fails to streaming MIPI DSI data

May 9, 2017, 4:31 am

≫ Next: TPS65094: PMU Signals glitch impact PMIC state

≪ Previous: OPT8241-CDK-EVM: obsolete parts.

Part Number:SN65DSI83

Tool/software: Linux

Hi TI Experts,

We are debugging a Android PAD project for our customer.

This project is an variation from former design. In previous design, the CPU is Qualcomm MSM8939, and the LCD display uses a MIPI DSI interface, everything works fine.

The new design changed the LCD display interface into LVDS(Flat-link) . So the connection is MSM8939 -> SN65DSI83 -> LVDS LCD display. And the SN65DSI83 uses MIPI D-PHY clock as the clock source.

We've made great efforts to make the LCD display to work. We've been testing the hardware by using the test pattern feature of SN65DSI83, finally by changing the D-PHY clock to continuous mode, we succeeded. The test pattern from SN65DSI83 is as follows:

By seeing the test pattern, we believe that the clock is OK(we uses an oscilloscope to show the clocks from D-PHY and LVDS, both to be correct), the parameters of the LCD display is matched. however, we still cannot see any outputs in the LCD by switch the test pattern feature off. The timing parameter of the MIPI DSI has been reviewed, and seems to be good.

The LCD resolution is 1280x800, the MIPI D-PHY clock is 200MHz, and in our settings, we divided it by 4 as the LVDS clock.

The SN65DSI83 register setting for the test pattern to work is written in a HTML script and can be found in the attachment.

Please give some advice, is there somthing else should be considered? (Please visit the site to view this file)

↧

TPS65094: PMU Signals glitch impact PMIC state

May 9, 2017, 4:39 am

≫ Next: CC2640: Manufacturer claims chipset problem relating to device reset

≪ Previous: Linux/SN65DSI83: generates test pattern OK, but fails to streaming MIPI DSI data

Part Number:TPS65094

Hi Team,

Sorry to bother you.

Please refer to below description, my customer mention Intel release sighting report to highlight PMU signals glitch during power on.

Do you know this glitch will impact or trigger TI PMIC state or not?

Thanks for your help and time.

↧

CC2640: Manufacturer claims chipset problem relating to device reset

May 9, 2017, 4:41 am

≫ Next: 3D Model needed for CBD Package

≪ Previous: TPS65094: PMU Signals glitch impact PMIC state

Part Number:CC2640

Recently we've been in talks with our manufacturer in China, who claim that they contacted a TI engineer regarding a fault observed in the operation of our devices.

The issue that has been reported by the manufacturer is that the device will become unresponsive after a varying amount of time. Taking the battery out and putting it back in seems to allow it to work again. We thought the issue was linked to an iCall abort problem stemming from managing BLE functions outside of the task, so this was fixed and a 'SysCtrlSystemReset()' was put in the AssertHandler() function to avoid device lock up (HAL_ASSERT_SPINLOCK) if it happened again.

We have rarely been able to reproduce the issue, but the manufacturer claims it persists, and that it can be traced to a chipset problem.

Here's an excerpt of a communication from the manufacturer:

please use “HCI_EXT_ResetSystemCmd(HCI_EXT_RESET_SYSTEM_HARD)”

Not only the forum,the TI enginner already confirm there is bug for this chipset if you ask them support,they will give you the real reason!

if we do as your old way will cause the product dead irregular,and some will cause the TICC2640 chipset damage,the TI enginner explain something about "flash",sorry,i am not clear what they say,if you ask them,they will explain clear

As you can see, communication is difficult and they are unable to fully convey the detail of their conversation with the TI engineer or the nature of the fault.

Could a TI employee with knowledge in this area please comment on the issue?

↧

3D Model needed for CBD Package

May 9, 2017, 4:42 am

≫ Next: TAS5342LA: Pop noise and Mid-Z sequence

≪ Previous: CC2640: Manufacturer claims chipset problem relating to device reset

Support Path: /Tools & software/Help find tools and software/Models & Simulation/Request new model/

Please provide a 3D model for the CBD package. TDA2Ex SoC for ADAS 17mm Package Silicon Rev 2.0

↧

TAS5342LA: Pop noise and Mid-Z sequence

May 9, 2017, 4:45 am

≫ Next: Compiler/PROCESSOR-SDK-AM437X: Permission Error with TI Compiler

≪ Previous: 3D Model needed for CBD Package

Part Number:TAS5342LA

I have question of TAS5342LA mid-z compatibility.

To reduce pop noise when powering up, mid-z sequence would be effective.

Is mid-z sequence the solution offered by external PWM processor, not TAS5342LA itself?

Do you have any idea to reduce pop noise while de-assering /RESET when powering up TAS5342LA?

Do you think it can be brought good impact by controlling RESET signal? (For example, ramp up RESET early etc...)

I now want the answer of TAS5342LA, not other device solution, sorry.

BestRegards

↧

Compiler/PROCESSOR-SDK-AM437X: Permission Error with TI Compiler

May 9, 2017, 4:45 am

≫ Next: Compiler: Inline once disabling with a compiler directive

≪ Previous: TAS5342LA: Pop noise and Mid-Z sequence

Part Number:PROCESSOR-SDK-AM437X

Tool/software: TI C/C++ Compiler

I created Project on AM437x IDK with TI Compiler
simply my project contain ِApp.c , i2c_app.c and i2c_app.h files
it gives me an error while compiling which is
fatal error #6001: cannot open file "C:/ti/am437x_sysbios_ind_sdk_2.0.0.2/sdk/starterware/include/utils": Permission denied
i already put this path in Compiler Directories

and this is the console log

**** Build of configuration Debug for project I2C_Examples_TI ****

"C:\\ti\\ccsv6\\utils\\bin\\gmake" -k all
'Building file: ../App.c'
'Invoking: ARM Compiler'
"C:/ti/ccsv6/tools/compiler/ti-cgt-arm_5.2.5/bin/armcl" -mv7A8 --code_state=32 --abi=eabi -me --include_path="C:/ti/am437x_sysbios_ind_sdk_2.0.0.2/sdk/os_drivers/include" --include_path="C:/ti/ccsv6/tools/compiler/ti-cgt-arm_5.2.5/include" --include_path="C:/ti/am437x_sysbios_ind_sdk_2.0.0.2/sdk/starterware/examples/example_utils" --include_path="C:/ti/am437x_sysbios_ind_sdk_2.0.0.2/sdk/starterware/include/am43xx/" --include_path="C:/ti/am437x_sysbios_ind_sdk_2.0.0.2/sdk/starterware/include/" --include_path="C:/ti/am437x_sysbios_ind_sdk_2.0.0.2/sdk/starterware/" --include_path="C:/ti/am437x_sysbios_ind_sdk_2.0.0.2/sdk/starterware/include/hw" -g --define=am4379 --diag_wrap=off --diag_warning=225 --display_error_number --preproc_with_compile --preproc_dependency="App.pp" "../App.c"
"C:\ti\am437x_sysbios_ind_sdk_2.0.0.2\sdk\starterware\include\dcard.h", line 212: warning #303-D: typedef name has already been declared (with same type)
"C:/ti/am437x_sysbios_ind_sdk_2.0.0.2/sdk/starterware/include/board.h", line 308: warning #303-D: typedef name has already been declared (with same type)
"C:/ti/am437x_sysbios_ind_sdk_2.0.0.2/sdk/starterware/include/board.h", line 321: warning #303-D: typedef name has already been declared (with same type)
"C:/ti/am437x_sysbios_ind_sdk_2.0.0.2/sdk/starterware/include/board.h", line 372: warning #303-D: typedef name has already been declared (with same type)
"C:/ti/am437x_sysbios_ind_sdk_2.0.0.2/sdk/starterware/include/board.h", line 394: warning #303-D: typedef name has already been declared (with same type)
"C:/ti/am437x_sysbios_ind_sdk_2.0.0.2/sdk/starterware/include/board.h", line 404: warning #303-D: typedef name has already been declared (with same type)
'Finished building: ../App.c'
' '
'Building file: ../i2c_app.c'
'Invoking: ARM Compiler'
"C:/ti/ccsv6/tools/compiler/ti-cgt-arm_5.2.5/bin/armcl" -mv7A8 --code_state=32 --abi=eabi -me --include_path="C:/ti/am437x_sysbios_ind_sdk_2.0.0.2/sdk/os_drivers/include" --include_path="C:/ti/ccsv6/tools/compiler/ti-cgt-arm_5.2.5/include" --include_path="C:/ti/am437x_sysbios_ind_sdk_2.0.0.2/sdk/starterware/examples/example_utils" --include_path="C:/ti/am437x_sysbios_ind_sdk_2.0.0.2/sdk/starterware/include/am43xx/" --include_path="C:/ti/am437x_sysbios_ind_sdk_2.0.0.2/sdk/starterware/include/" --include_path="C:/ti/am437x_sysbios_ind_sdk_2.0.0.2/sdk/starterware/" --include_path="C:/ti/am437x_sysbios_ind_sdk_2.0.0.2/sdk/starterware/include/hw" -g --define=am4379 --diag_wrap=off --diag_warning=225 --display_error_number --preproc_with_compile --preproc_dependency="i2c_app.pp" "../i2c_app.c"
'Finished building: ../i2c_app.c'
' '
'Building target: I2C_Examples_TI.out'
'Invoking: ARM Linker'
"C:/ti/ccsv6/tools/compiler/ti-cgt-arm_5.2.5/bin/armcl" -mv7A8 --code_state=32 --abi=eabi -me -g --define=am4379 --diag_wrap=off --diag_warning=225 --display_error_number -z -m"I2C_Examples_TI.map" --heap_size=0x800 --stack_size=0x800 -i"C:/ti/ccsv6/tools/compiler/ti-cgt-arm_5.2.5/lib" -i"C:/ti/am437x_sysbios_ind_sdk_2.0.0.2/sdk/starterware/binary/soc/lib/am43xx-evm/a9/ccs/am43xx_release" -i"C:/ti/am437x_sysbios_ind_sdk_2.0.0.2/sdk/starterware/binary/utils/lib/am43xx-evm/a9/ccs/am43xx_release" -i"C:/ti/am437x_sysbios_ind_sdk_2.0.0.2/sdk/starterware/binary/device/lib/am43xx-evm/a9/ccs/am43xx_release" -i"C:/ti/am437x_sysbios_ind_sdk_2.0.0.2/sdk/starterware/binary/dal/lib/am43xx-evm/a9/ccs/am43xx_release" -i"C:/ti/am437x_sysbios_ind_sdk_2.0.0.2/sdk/starterware/binary/board/lib/am43xx-evm/a9/ccs/am43xx_release" -i"C:/ti/am437x_sysbios_ind_sdk_2.0.0.2/sdk/starterware/examples/example_utils" -i"C:/ti/am437x_sysbios_ind_sdk_2.0.0.2/sdk/starterware/include/" -i"C:/ti/am437x_sysbios_ind_sdk_2.0.0.2/sdk/starterware/include/hw" -i"C:/ti/am437x_sysbios_ind_sdk_2.0.0.2/sdk/starterware/include/am43xx/" --reread_libs --display_error_number --diag_wrap=off --warn_sections --xml_link_info="I2C_Examples_TI_linkInfo.xml" --rom_model -o "I2C_Examples_TI.out" "./App.obj" "./i2c_app.obj" "../AM437x.cmd" -l"libc.a" -l"utils" -l"c" -l"example_utils"
<Linking>
fatal error #6001: cannot open file "C:/ti/am437x_sysbios_ind_sdk_2.0.0.2/sdk/starterware/include/utils": Permission denied

>> Compilation failure
gmake: *** [I2C_Examples_TI.out] Error 1
gmake: Target `all' not remade because of errors.

**** Build Finished ****

↧

Compiler: Inline once disabling with a compiler directive

May 9, 2017, 4:47 am

≫ Next: TPS65982: Detection of USB2.0 or USB 3.0

≪ Previous: Compiler/PROCESSOR-SDK-AM437X: Permission Error with TI Compiler

Tool/software: TI C/C++ Compiler

Hello

We are using the c2000 environment. I need an information about the inline directive. When in the advanced optimization menu of the code composer the "inline function is called once activated, is it then possibly to suppress this feature. In our case with we have a function which is called only once directly. But the calling function is called several times. Is it possible to suppress the inline with a directive or how handles the compiler such a case.

Thanks

Reto

↧

TPS65982: Detection of USB2.0 or USB 3.0

May 9, 2017, 4:51 am

≫ Next: cc2541: CC2541 ble software hex file protection

≪ Previous: Compiler: Inline once disabling with a compiler directive

Part Number:TPS65982

Hi Team,

My customer would like to know which data rate connection(USB2.0 or USB3.0) is established on USB line. And they hope TPS65982 or HD3SS460 has any indicator functions(like status register).

Does TPS65982 have such function to distinguish established standard on USB line?

I think it might be impassible because the established connection doesn't depends on physical layer but link layer. But let me double check just in case.

Regards,

Takashi Onawa

↧

cc2541: CC2541 ble software hex file protection

May 9, 2017, 4:55 am

≫ Next: CCS/ADS1292: ADS1292 channel 1 read issue

≪ Previous: TPS65982: Detection of USB2.0 or USB 3.0

Part Number:cc2541

Hi ,

Urgent question!!!!!!!!!!

We have developed a product using CC2541 ic. Our product is ready for production now.

I want to know how i can protect software/hex file from being copied. As you might have idea that in "SmartRF Flash Programmer" we have option to "Read Flash in hex file". So i am worried that anyone can read hex file if they get to know the part number.

Is there any way to protect the software from being copied? any protection or encryption method in stack itself.

Looking forward to reply from you.

↧