LMG3410: Voltage at RDRV Pin
CCS/AWR1642: Runtime error
Part Number:AWR1642
Tool/software: Code Composer Studio
Hello,
I have been trying to run the mmw demo on the AWR1642 BOOST. I made some changes of this demo, which include the modification of the function 'MmwDemo_interFrameProcessing' and the uasge of a free EDMA channel to transfer data. There is no error when I rebuilt the demo and load it to the EVM. However, when I run this demo, the CCS aborts and writes the following errors:
As the second error says, it is the assertion failure in line 1698 in "mss_main.c". I thought maybe it is the 'MMWDEMO_BSS_CPUFAULT_EVT' status that causes the assertion failure.
But I donn't know how to understand the BSS_CPUFAULT and what condition could trigger this event? Could you help me?
Also, I know you and your team members are very experienced in debugging AWR1642 demo. So could you give me some advice on how to solve this problem?
. Thank you!
William
TCA6424A: What is the rise and fall time of the Port Pins when output changes?
Part Number:TCA6424A
Hello,
I was looking through the datasheet, and it doesn't specify what the rise and fall time of the device's port pins are with a change to output?
Could you specify what this is and what load it was tested with?
Thank you,
Louie
MSP432P401R: PWM not updating
Part Number:MSP432P401R
I am trying to build a car with obstruction detection using analog output proximity sensors. The problem is whenever I integrate the PWM module for moving the vehicle and the proximity sensors, the PWM does not update (I measured the with an oscilloscope). The weird thing is that whenever I step into the program line by line, the PWM updates but if irun the program it doesnt update.
Below is the code I currently have.
Timer_A_PWMConfig servoConfig = { TIMER_A_CLOCKSOURCE_SMCLK, TIMER_A_CLOCKSOURCE_DIVIDER_1, 1300, TIMER_A_CAPTURECOMPARE_REGISTER_1, TIMER_A_OUTPUTMODE_RESET_SET, 94 //center }; /* Timer_A Servo PWM Configuration Parameter */ Timer_A_PWMConfig motorConfig = { TIMER_A_CLOCKSOURCE_SMCLK, TIMER_A_CLOCKSOURCE_DIVIDER_1, 1300, TIMER_A_CAPTURECOMPARE_REGISTER_2, TIMER_A_OUTPUTMODE_RESET_SET, 75 }; int main(void) { /* Halting WDT */ MAP_WDT_A_holdTimer(); MAP_Interrupt_disableSleepOnIsrExit(); /* Zero-filling buffer */ memset(resultsBuffer, 0x00, 8); /* Setting MCLK to REFO at 128Khz for LF mode * Setting SMCLK to 64Khz */ MAP_CS_setReferenceOscillatorFrequency(CS_REFO_128KHZ); //MAP_CS_initClockSignal(CS_MCLK, CS_REFOCLK_SELECT, CS_CLOCK_DIVIDER_1); MAP_CS_initClockSignal(CS_SMCLK, CS_REFOCLK_SELECT, CS_CLOCK_DIVIDER_2); MAP_PCM_setPowerState(PCM_AM_LF_VCORE0); /* Configuring GPIO2.4 as peripheral output for PWM and P1.1 for button * interrupt */ MAP_GPIO_setAsPeripheralModuleFunctionOutputPin(GPIO_PORT_P2, GPIO_PIN4,GPIO_PRIMARY_MODULE_FUNCTION); MAP_GPIO_setAsPeripheralModuleFunctionOutputPin(GPIO_PORT_P2, GPIO_PIN5,GPIO_PRIMARY_MODULE_FUNCTION); /* Configuring Timer_A to have a period of approximately 500ms and * an initial duty cycle of 10% of that (3200 ticks) */ MAP_Timer_A_generatePWM(TIMER_A0_BASE, &servoConfig); /* Configuring Timer_A to have a period of approximately 500ms and * an initial duty cycle of 10% of that (3200 ticks) */ MAP_Timer_A_generatePWM(TIMER_A0_BASE, &motorConfig); /* Configuring GPIO2.4 as peripheral output for PWM and P1.1 for button * interrupt */ MAP_GPIO_setAsPeripheralModuleFunctionOutputPin(GPIO_PORT_P2, GPIO_PIN4,GPIO_PRIMARY_MODULE_FUNCTION); MAP_GPIO_setAsPeripheralModuleFunctionOutputPin(GPIO_PORT_P2, GPIO_PIN5,GPIO_PRIMARY_MODULE_FUNCTION); /* Initializing ADC (MCLK/64/8) */ MAP_ADC14_enableModule(); MAP_ADC14_initModule(ADC_CLOCKSOURCE_MCLK, ADC_PREDIVIDER_64, ADC_DIVIDER_8, 0); /* Configuring GPIOs for Analog In */ MAP_GPIO_setAsPeripheralModuleFunctionInputPin(GPIO_PORT_P5, GPIO_PIN5 | GPIO_PIN4 | GPIO_PIN3 | GPIO_PIN2 | GPIO_PIN1 | GPIO_PIN0, GPIO_TERTIARY_MODULE_FUNCTION); MAP_GPIO_setAsPeripheralModuleFunctionInputPin(GPIO_PORT_P4, GPIO_PIN7 | GPIO_PIN6, GPIO_TERTIARY_MODULE_FUNCTION); MAP_GPIO_setAsOutputPin(GPIO_PORT_P2, GPIO_PIN1); MAP_GPIO_setOutputLowOnPin(GPIO_PORT_P2, GPIO_PIN1); /* Configuring ADC Memory (ADC_MEM0 - ADC_MEM7 (A0 - A2) with repeat)*/ MAP_ADC14_configureMultiSequenceMode(ADC_MEM0, ADC_MEM2, true); MAP_ADC14_configureConversionMemory(ADC_MEM0, ADC_VREFPOS_INTBUF_VREFNEG_VSS, ADC_INPUT_A0, false); MAP_ADC14_configureConversionMemory(ADC_MEM1, ADC_VREFPOS_INTBUF_VREFNEG_VSS, ADC_INPUT_A1, false); MAP_ADC14_configureConversionMemory(ADC_MEM2, ADC_VREFPOS_INTBUF_VREFNEG_VSS, ADC_INPUT_A6, false); /* Enabling the interrupt when a conversion on channel 7 (end of sequence) * is complete and enabling conversions */ MAP_ADC14_enableInterrupt(ADC_INT2); /* Enabling Interrupts */ MAP_Interrupt_enableInterrupt(INT_ADC14); MAP_Interrupt_enableMaster(); /* Setting up the sample timer to automatically step through the sequence * convert. */ MAP_ADC14_enableSampleTimer(ADC_AUTOMATIC_ITERATION); /* Triggering the start of the sample */ MAP_ADC14_enableConversion(); MAP_ADC14_toggleConversionTrigger(); __delay_cycles(20000); MAP_Timer_A_generatePWM(TIMER_A0_BASE, &motorConfig); motorConfig.dutyCycle = 90; /* Going to sleep */ while (1) { //MAP_Timer_A_generatePWM(TIMER_A0_BASE, &motorConfig); /* if(ADC_SampleComplete == 1){ if((resultsBuffer[0] > 11000) | (resultsBuffer[1] > 11000) | (resultsBuffer[2] > 11000)){ motorConfig.dutyCycle = 70; MAP_GPIO_setOutputHighOnPin(GPIO_PORT_P2, GPIO_PIN1); //MAP_Timer_A_generatePWM(TIMER_A0_BASE, &motorConfig); } else{ MAP_GPIO_setOutputLowOnPin(GPIO_PORT_P2, GPIO_PIN1); motorConfig.dutyCycle = 97; // MAP_Timer_A_generatePWM(TIMER_A0_BASE, &motorConfig); } } */ // MAP_PCM_gotoLPM0(); } } /* This interrupt is fired whenever a conversion is completed and placed in * ADC_MEM7. This signals the end of conversion and the results array is * grabbed and placed in resultsBuffer */ void ADC14_IRQHandler(void) { uint64_t status; status = MAP_ADC14_getEnabledInterruptStatus(); ADC_SampleComplete = 0; if(status & ADC_INT2) { resultsBuffer[0] = MAP_ADC14_getResult(ADC_MEM0); resultsBuffer[1] = MAP_ADC14_getResult(ADC_MEM1); resultsBuffer[2] = MAP_ADC14_getResult(ADC_MEM2); ADC_SampleComplete = 1; if((resultsBuffer[0] > 11000) | (resultsBuffer[1] > 11000) | (resultsBuffer[2] > 11000)){ motorConfig.dutyCycle = 70; MAP_GPIO_setOutputHighOnPin(GPIO_PORT_P2, GPIO_PIN1); MAP_Timer_A_generatePWM(TIMER_A0_BASE, &motorConfig); } else { MAP_GPIO_setOutputLowOnPin(GPIO_PORT_P2, GPIO_PIN1); motorConfig.dutyCycle = 97; MAP_Timer_A_generatePWM(TIMER_A0_BASE, &motorConfig); } } MAP_ADC14_clearInterruptFlag(status); }
LAUNCHXL-F28379D: The Sine wave that I sample using DAC-B and output from GPIO pin 70 disappears after ~100 seconds
Part Number:LAUNCHXL-F28379D
I am using Simulink Embedded Coder to program my microcontroller, I am trying to generate a 25kHz sine wave for my speaker.
I am monitoring the signal by connecting an oscilloscope to GPIO pin 70.
When the frequency is 25kHz there is no signal. The result is as follows:
Then I tested the system by reducing the frequency to 250Hz. The result is as follows:
Then I changed the step size from "auto" to 1/(5e5) and the result is as follows:
But as I said this signal disappears in about 100 seconds. In the video below, I captured this weird behaviour.
(Please visit the site to view this video)
Why is this signal not continuous and it disappears after a while? Why does i not appear like a proper sine wave when the fixed step size is configured as "auto"?
Finally I will share some screenshots to help with the troubleshooting.
This is my code. First I generate a sine wave with Amplitude 1 and Frequency 250Hz. Then I amplify it by 2047 times and shift it up by 2047 in order to create a sine wave in the range of 0-2^12..
This is the configuration parameters window where I changed the Fixed-step size. Note the solver type is "Fixed-step" and Solver Type is "discrete (no continuous states)".
CC2540: UART Rx side on CC2540 getting garbage data
Part Number:CC2540
Hi Team,
I have been searching e2e posts for corrupt UART data; most posts seem to address Tx side while my issue is with Rx side on CC2540 (external Tx side pretty well tested and flushed out).
I found this e2e post which essentially suggests that if you are using UART w/ DMA, you should ensure the HCI_EXT_ClkDivOnHaltCmd()function is not called; even though not using DMA I tried this but no luck.
two questions:
1) Any idea what can be causing me to receive garbage data in ~5% of my messages?
2) when it comes to commenting out HCI_EXT_ClkDivOnHaltCmd() function, I see the comments suggests MCU is halted when network processor is active; is this true and could this be contrinuting to the issue I am seeing?
// Enable clock divide on halt
// This reduces active current while radio is active and CC254x MCU
// is halted
// HCI_EXT_ClkDivOnHaltCmd( HCI_EXT_ENABLE_CLK_DIVIDE_ON_HALT );
LAUNCHXL-CC1310: Sniffer connection problem
Part Number:LAUNCHXL-CC1310
Hi.
I am trying to set up a sniffer fw on LAUNCHXL-CC1310 to sniff sub1ghz packets coming from CC1350 sensortag.
I used C:/ti/simplelink_cc13x0_sdk_1_30_00_06/tools/ti154stack/TiWsPc2/sniffer_fw/bin/sniffer_fw_gfsk_50kbps_868_915.hex with Flash Programmer to flash the launchxl, and it flashed successfully.
When the device is turned on, the green led is blinking and I can see in UART the string "TI Packet Sniffer ver.1.0.0" printed every second.
I installed smartRF packet-sniffer 2 from TI but when I turn it on, it cannot find any devices, also when I press "Search for new Devices".
Can you please help, How do I set up the sniffer?
CC2640R2F: alternatives for balun
Part Number:CC2640R2F
My customer is currently using the Murata Balun with the CC2640R2 . This part now has a long lead time. Can you confirm if this Johanson is an acceptable alternate?
Murata
Johanson
Do you have other options to suggest?
Thank you!
OPT3006: Android
LAUNCHXL-CC1350: Unable to setup appropriate rf-settings
Part Number:LAUNCHXL-CC1350
Greetings!
I have for a while had the ambition to port an old project built with CC1111 and RPi
and use the LAUNCHXL-CC1350 and create a bridge between ProrietaryRF-BLE
but what I initially though would be the simplest task have become a stopper.
I'm unable to setup the right RF-settings and I have nearly tried all that I have
read in this forum and tech-documents, can't figure out why. I succeed in recieving
data but it is not correct. I really appreciate all help.
CC1111 correct rf-settings:
// Address Config = No address check // Base Frequency = 920.079712 // CRC Enable = true // Carrier Frequency = 920.079712 // Channel Number = 0 // Channel Spacing = 199.951172 // Data Rate = 17.9901 // Deviation = 20.507813 // Device Address = 0 // Manchester Enable = false // Modulated = true // Modulation Format = 2-FSK // PA Ramping = false // Packet Length = 255 // Packet Length Mode = Variable packet length mode. Packet length configured by the first byte after sync word // Preamble Count = 2 // RX Filter BW = 250.000000 // Sync Word Qualifier Mode = 15/16 + carrier-sense above threshold // TX Power = 0 // Whitening = false // Rf settings for CC1111 RF_SETTINGS code rfSettings = { 0x05, // PKTCTRL0 Packet Automation Control 0x06, // FSCTRL1 Frequency Synthesizer Control 0x26, // FREQ2 Frequency Control Word, High Byte 0x56, // FREQ1 Frequency Control Word, Middle Byte 0x2F, // FREQ0 Frequency Control Word, Low Byte 0x69, // MDMCFG4 Modem configuration 0x89, // MDMCFG3 Modem Configuration 0x05, // MDMCFG2 Modem Configuration 0x03, // MDMCFG1 Modem Configuration 0x11, // MDMCFG0 Modem Configuration 0x36, // DEVIATN Modem Deviation Setting 0x18, // MCSM0 Main Radio Control State Machine Configuration 0x16, // FOCCFG Frequency Offset Compensation Configuration 0x43, // AGCCTRL2 AGC Control 0xE9, // FSCAL3 Frequency Synthesizer Calibration 0x2A, // FSCAL2 Frequency Synthesizer Calibration 0x00, // FSCAL1 Frequency Synthesizer Calibration 0x1F, // FSCAL0 Frequency Synthesizer Calibration 0x31, // TEST1 Various Test Settings 0x09, // TEST0 Various Test Settings 0x8E, // PA_TABLE0 PA Power Setting 0 };
CC1350 NOT correct settings(one of 31 tweaked versions):
//********************************************************************************* // Generated by SmartRF Studio version 2.8.0 ( build #41) // Compatible with SimpleLink SDK version: CC13x0 SDK 1.60.xx.xx // Device: CC1350 Rev. 2.1 // //********************************************************************************* //********************************************************************************* // Parameter summary // Address: off // Address0: 0xAA // Address1: 0xBB // Frequency: 920.07970 MHz // Data Format: Serial mode disable // Deviation: 20.000 kHz // pktLen: 30 // 802.15.4g Mode: off // Select bit order to transmit PSDU octets:: 1 // Packet Length Config: Variable // Max Packet Length: 255 // Packet Length: 128 // RX Filter BW: 311 kHz // Symbol Rate: 17.99927 kBaud // Sync Word Length: 16 Bits // TX Power: 14 dBm (requires define CCFG_FORCE_VDDR_HH = 1 in ccfg.c, see CC13xx/CC26xx Technical Reference Manual) // Whitening: No whitening #include <ti/devices/DeviceFamily.h> #include DeviceFamily_constructPath(driverlib/rf_mailbox.h) #include DeviceFamily_constructPath(driverlib/rf_common_cmd.h) #include DeviceFamily_constructPath(driverlib/rf_prop_cmd.h) #include <ti/drivers/rf/RF.h> #include DeviceFamily_constructPath(rf_patches/rf_patch_cpe_genfsk.h) #include DeviceFamily_constructPath(rf_patches/rf_patch_rfe_genfsk.h) #include "smartrf_settings.h" // TI-RTOS RF Mode Object RF_Mode RF_prop = { .rfMode = RF_MODE_PROPRIETARY_SUB_1, .cpePatchFxn = &rf_patch_cpe_genfsk, .mcePatchFxn = 0, .rfePatchFxn = &rf_patch_rfe_genfsk, }; // Overrides for CMD_PROP_RADIO_DIV_SETUP static uint32_t pOverrides[] = { // override_use_patch_prop_genfsk.xml // PHY: Use MCE ROM bank 4, RFE RAM patch MCE_RFE_OVERRIDE(0,4,0,1,0,0), // override_synth_prop_863_930_div5.xml // Synth: Set recommended RTRIM to 7 HW_REG_OVERRIDE(0x4038,0x0037), // Synth: Set Fref to 4 MHz (uint32_t)0x000684A3, // Synth: Configure fine calibration setting HW_REG_OVERRIDE(0x4020,0x7F00), // Synth: Configure fine calibration setting HW_REG_OVERRIDE(0x4064,0x0040), // Synth: Configure fine calibration setting (uint32_t)0xB1070503, // Synth: Configure fine calibration setting (uint32_t)0x05330523, // Synth: Set loop bandwidth after lock to 20 kHz (uint32_t)0x0A480583, // Synth: Set loop bandwidth after lock to 20 kHz (uint32_t)0x7AB80603, // Synth: Configure VCO LDO (in ADI1, set VCOLDOCFG=0x9F to use voltage input reference) ADI_REG_OVERRIDE(1,4,0x9F), // Synth: Configure synth LDO (in ADI1, set SLDOCTL0.COMP_CAP=1) ADI_HALFREG_OVERRIDE(1,7,0x4,0x4), // Synth: Use 24 MHz XOSC as synth clock, enable extra PLL filtering (uint32_t)0x02010403, // Synth: Configure extra PLL filtering (uint32_t)0x00108463, // Synth: Increase synth programming timeout (0x04B0 RAT ticks = 300 us) (uint32_t)0x04B00243, // override_phy_rx_aaf_bw_0xd.xml // Rx: Set anti-aliasing filter bandwidth to 0xD (in ADI0, set IFAMPCTL3[7:4]=0xD) ADI_HALFREG_OVERRIDE(0,61,0xF,0xD), // override_phy_gfsk_rx.xml // Rx: Set LNA bias current trim offset to 3 (uint32_t)0x00038883, // Rx: Freeze RSSI on sync found event HW_REG_OVERRIDE(0x6084,0x35F1), // override_phy_gfsk_pa_ramp_agc_reflevel_0x1a.xml // Tx: Configure PA ramping setting (0x41). Rx: Set AGC reference level to 0x1A. HW_REG_OVERRIDE(0x6088,0x411A), // Tx: Configure PA ramping setting HW_REG_OVERRIDE(0x608C,0x8213), // override_phy_rx_rssi_offset_5db.xml // Rx: Set RSSI offset to adjust reported RSSI by +5 dB (uint32_t)0x00FB88A3, // TX power override // Tx: Set PA trim to max (in ADI0, set PACTL0=0xF8) ADI_REG_OVERRIDE(0,12,0xF8), (uint32_t)0xFFFFFFFF, }; // CMD_PROP_RADIO_DIV_SETUP // Proprietary Mode Radio Setup Command for All Frequency Bands rfc_CMD_PROP_RADIO_DIV_SETUP_t RF_cmdPropRadioDivSetup = { .commandNo = 0x3807, .status = 0x0000, .pNextOp = 0, // INSERT APPLICABLE POINTER: (uint8_t*)&xxx .startTime = 0x00000000, .startTrigger.triggerType = 0x0, .startTrigger.bEnaCmd = 0x0, .startTrigger.triggerNo = 0x0, .startTrigger.pastTrig = 0x0, .condition.rule = 0x1, .condition.nSkip = 0x0, .modulation.modType = 0x0, .modulation.deviation = 0x50, .symbolRate.preScale = 0xF, .symbolRate.rateWord = 0x2E14, .rxBw = 0x29, .preamConf.nPreamBytes = 0x2, .preamConf.preamMode = 0x0, .formatConf.nSwBits = 0x10, .formatConf.bBitReversal = 0x0, .formatConf.bMsbFirst = 0x1, .formatConf.fecMode = 0x0, .formatConf.whitenMode = 0x0, .config.frontEndMode = 0x0, .config.biasMode = 0x1, .config.analogCfgMode = 0x0, .config.bNoFsPowerUp = 0x0, .txPower = 0xAB3F, .pRegOverride = pOverrides, .centerFreq = 0x0398, .intFreq = 0x8000, .loDivider = 0x05, }; // CMD_FS // Frequency Synthesizer Programming Command rfc_CMD_FS_t RF_cmdFs = { .commandNo = 0x0803, .status = 0x0000, .pNextOp = 0, // INSERT APPLICABLE POINTER: (uint8_t*)&xxx .startTime = 0x00000000, .startTrigger.triggerType = 0x0, .startTrigger.bEnaCmd = 0x0, .startTrigger.triggerNo = 0x0, .startTrigger.pastTrig = 0x0, .condition.rule = 0x1, .condition.nSkip = 0x0, .frequency = 0x0398, .fractFreq = 0x1467, .synthConf.bTxMode = 0x0, .synthConf.refFreq = 0x0, .__dummy0 = 0x00, .__dummy1 = 0x00, .__dummy2 = 0x00, .__dummy3 = 0x0000, }; // CMD_PROP_TX // Proprietary Mode Transmit Command rfc_CMD_PROP_TX_t RF_cmdPropTx = { .commandNo = 0x3801, .status = 0x0000, .pNextOp = 0, // INSERT APPLICABLE POINTER: (uint8_t*)&xxx .startTime = 0x00000000, .startTrigger.triggerType = 0x0, .startTrigger.bEnaCmd = 0x0, .startTrigger.triggerNo = 0x0, .startTrigger.pastTrig = 0x0, .condition.rule = 0x1, .condition.nSkip = 0x0, .pktConf.bFsOff = 0x0, .pktConf.bUseCrc = 0x1, .pktConf.bVarLen = 0x1, .pktLen = 0x80, // SET APPLICATION PAYLOAD LENGTH .syncWord = 0x0000D391, .pPkt = 0, // INSERT APPLICABLE POINTER: (uint8_t*)&xxx }; // CMD_PROP_RX // Proprietary Mode Receive Command rfc_CMD_PROP_RX_t RF_cmdPropRx = { .commandNo = 0x3802, .status = 0x0000, .pNextOp = 0, // INSERT APPLICABLE POINTER: (uint8_t*)&xxx .startTime = 0x00000000, .startTrigger.triggerType = 0x0, .startTrigger.bEnaCmd = 0x0, .startTrigger.triggerNo = 0x0, .startTrigger.pastTrig = 0x0, .condition.rule = 0x1, .condition.nSkip = 0x0, .pktConf.bFsOff = 0x0, .pktConf.bRepeatOk = 0x0, .pktConf.bRepeatNok = 0x0, .pktConf.bUseCrc = 0x1, .pktConf.bVarLen = 0x1, .pktConf.bChkAddress = 0x0, .pktConf.endType = 0x0, .pktConf.filterOp = 0x0, .rxConf.bAutoFlushIgnored = 0x0, .rxConf.bAutoFlushCrcErr = 0x0, .rxConf.bIncludeHdr = 0x1, .rxConf.bIncludeCrc = 0x0, .rxConf.bAppendRssi = 0x0, .rxConf.bAppendTimestamp = 0x0, .rxConf.bAppendStatus = 0x1, .syncWord = 0x0000D391, .maxPktLen = 0xFF, // MAKE SURE DATA ENTRY IS LARGE ENOUGH .address0 = 0xAA, .address1 = 0xBB, .endTrigger.triggerType = 0x1, .endTrigger.bEnaCmd = 0x0, .endTrigger.triggerNo = 0x0, .endTrigger.pastTrig = 0x0, .endTime = 0x00000000, .pQueue = 0, // INSERT APPLICABLE POINTER: (dataQueue_t*)&xxx .pOutput = 0, // INSERT APPLICABLE POINTER: (uint8_t*)&xxx };
CCS/LAUNCHXL-CC2640R2: 3 CC264PBA v1.1a wirelessly communicate to LAUNCHXL-CC2640R2
Part Number:LAUNCHXL-CC2640R2
Tool/software: Code Composer Studio
I am trying to get 3 cc264PBA v1.1 wireless module to transmit, as slaves, values from an IMU to a master LAUNCHXL-CC2640R2 that connects to the CPU where it is used to register movement, and I keep receiving target errors. I am here to inquire about any documentation that could prove helpful or any other help that could be offered.
LMP91000: Configurations
Part Number:LMP91000
Dear Community,
I am trying to configuration the lmp91000 for work with the sensors O2-M2 and ETO-A1 both of Alphasense.
The settings that I used for the sensor O2-M2 are as follows:
LMP91000_TIA_GAIN_350K | LMP91000_RLOAD_100OHM,
LMP91000_REF_SOURCE_INT | LMP91000_INT_Z_50PCT | LMP91000_BIAS_SIGN_POS | LMP91000_BIAS_0PCT,
LMP91000_FET_SHORT_DISABLED | LMP91000_OP_MODE_AMPEROMETRIC
And the settings that I used for the sensor ETO-A1 are as follows:
LMP91000_TIA_GAIN_350K | LMP91000_RLOAD_33OHM,
LMP91000_REF_SOURCE_INT | LMP91000_INT_Z_50PCT | LMP91000_BIAS_SIGN_POS | LMP91000_BIAS_6PCT,
LMP91000_FET_SHORT_DISABLED | LMP91000_OP_MODE_AMPEROMETRIC
My problems are the following:
I'm not sure the values for TIA_GAIN, REF_SOURCE, INT_Z and FET_SHORT, ¿how I can know the values for these parameters?
TMS320F28377S: Question about TMS320F28377S internal voltage regulator
Part Number:TMS320F28377S
Hello,
I'm confused by TMS320F28377S's internal voltage regulator. It looks like it is not supported anymore. But when I enable it by pulling down VREFENZ pin, the VDD pin gives me 1.2V. Is there still a voltage regulator inside F28377s? If so, what is the problem to use this voltage regulator? Thanks!
Yang
CCS/CCSTUDIO: Burn using CCStudio 8 without uniflash
TPS92518: EVM PWM jumper name typo?
Part Number:TPS92518
Hi
I would like to double confirmed about the pwm jumper name.
On schematic the PWM are controlled with J6 and J13.
But on the setting description is J13 and J15, is it a typo?
Thank you.
Best Regards,
Pearl Lin (FAE) 林瑋萍
Texas Instruments Incorporated (Kaohsiung)
CC2650: CC2650STK
Part Number:CC2650
Hi, dear sirs:
We need to read the location of the sensor tag, so we are using the barometer to find the altitud of the tag, but the data looks out of range, is there a procedure to calibrate it?
TNK
Miguel
CCS/TMS320F28032: High Resolution PWM Period
Part Number:TMS320F28032
Tool/software: Code Composer Studio
Hey Everyone!
I'm stuck trying to compute the fractional bits of the TBPRDHR. I'm not sure how to realize this inside the code. Can anyone help?
Thanks,
Christian
DP83867E: DP83867E Phy Address
Part Number:DP83867E
Is there a workaround to set the Phy Address to 19h ?
Datasheet shows only phy_addrs[3..0] to be configurable with phy_addrs[4] set to "0"
thanks
CCS/TMS320VC5421: Build & debug tools for the VC5421
Part Number:TMS320VC5421
Tool/software: Code Composer Studio
What tools options do we have for working with the TMS320VC5421?
I have not been able to find an emulator or any CCS support. How far into the newer CCS versions did we support the VC5421, or C54x in general?
Thanks and regards,
RandyP
Discovery 1100 Controller Board
Hi,
We have an old DMD device (0.7 XGA DDR DMD) which comes with the board, Discovery 1100. I tried to install the drivers on Win 10 and the attempt is failed, however, the software seems working, other supporting software are not communicating with the device.
I think our current DMD device is sufficiently good for our research purposes, it is just the board that encounters problem with the new operating system and does not function.
I wonder if it is possible to update the board and supporting software and mount the old DMD on the new board? If we do so, will it work with new operating systems (like Win 10 or 7)?
If yes, please provide me the links/information of the person/company whom I can contact with to replace our board, also we would like to figure out about the prices in this case.
In addition, it would be nice to know whether there would be some discount options in case of returning the whole old device (including the DMD) to the company and order a new board with newer DMD chip-sets?
thanks,