↧
AM5728: AM5728 Block Diagram
↧
PGA460: Air-Coupled Ultrasonic Transducers & Transformers Listing
Part Number:PGA460
Air-Coupled Ultrasonic Transducers & Transformers Listing for PGA460
The following tables lists readily available ultrasonic transducers and transformers which are compatible with the PGA460 ultrasonic sensing signal conditioner. The MS Excel version of the table is available here for advanced filtering and sorting:
(Please visit the site to view this file)
| Air-Coupled Ultrasonic Transducers Revision: Initial Release - Date: 08/24/2017 | ||||||
| Manufacturer | Part Number | Construction | Resonant Frequency (kHz) | Max Input Voltage (Vp-p) | Beam Angle (X° × Y°) | Transceive |
| Audiowell | 3T(R)40100B01-TS009L01 | Open | 40 ± 1.0 | 30 Vrms | 70 x 70 | Y |
| Audiowell | 8T4012OA01-TS003L01 | Open | 40 ± 1.0 | 30 Vrms | 70 x 70 | Y |
| Audiowell | AW19T40-10OB01-01 | Open | 40 ± 1.0 | 40 | 90 x 90 | Y |
| Audiowell | AW8T40-10OA00 | Open | 40 ± 1.0 | 30 Vrms | 90 x 90 | Y |
| Audiowell | AW8T40-12OB01-00 | Open | 40 ± 1.0 | 20 Vrms | 70 x 70 | Y |
| Audiowell | AW8T40-16OA00 | Open | 40 ± 1.0 | 20 Vrms | 80 x 80 | Y |
| Audiowell | AW8TR40-16OC01-01 | Open | 40 ± 1.0 | 20 Vrms | 55 x 55 | Y |
| Audiowell APA | T/R48-15.5H279Z-L12-01 | Closed | 48 ± 1.0 | 160 | 60 x 60 | Y |
| Audiowell APA | T/R58-15F279Z-L12-01 | Closed | 58 ± 1.0 | 140 | 90 x 45 | Y |
| Audiowell UPA | T/R40-14.4A | Closed | 40 ± 1.0 | 140 | 70 x 70 | Y |
| Audiowell UPA | T/R40-14U | Closed | 40 ± 1.0 | 140 | 120 x 70 | Y |
| Audiowell UPA | T/R40-14U324-01 | Closed | 55 ± 1.0 | 140 | 120 x 70 | Y |
| Audiowell UPA | T/R48-14C279Z-L12-02 | Closed | 48 ± 1.0 | 140 | 100 x 50 | Y |
| Audiowell UPA | T/R55-15.5E279Z-L12-01 | Closed | 55 ± 1.0 | 140 | 90 x 45 | Y |
| Audiowell UPA | T/R60-10H | Closed | 60 ± 1.0 | 140 | 80 x 80 | Y |
| Hurricane | TA00840-10 | Closed | 80 ± 2.0 | 800 | 40 x 40 | Y |
| Kobitone | 255-400PT160-ROX | Open | 40 ± 1.0 | 20 Vrms | 40 x 40 | Y |
| Massa | E-188/220 (200639-501) | Closed | 220 | TBD | 15 x 15 | Y |
| Massa | TR-89 Type 40 | Closed | 40 ± 2.0 | 35 (sqr); 45 (sine); 200mW | 20 x 20 | Y |
| Multicomp | MCUSD14A40S09RS-30C | Closed | 40 ± 1.0 | 160 | 110 x 50 | Y |
| Multicomp | MCUSD14A48S09RS-30C | Closed | 48 ± 1.1 | 160 | 110 x 50 | Y |
| Multicomp | MCUSD16P40B12RO | Open | 40 ± 1.0 | 120 | 50 x 50 | Y |
| Multicomp | MCUSD17.5A48S11RS-30C | Closed | 48 ± 1.0 | 160 | 110 x 50 | Y |
| Multicomp | MCUSD18A40S09RS-30C | Closed | 40 ± 1.0 | 160 | 110 x 50 | Y |
| Multicomp | MCUSD19A175B11.5RS | Closed | 175 ± 10.0 | 500 | 7 x 7 | Y |
| Multicomp | MCUSD25P200B10.7RS-30C | Closed | 200 ± 8.0 | TBD | 14 x 14 | Y |
| Multicomp | MCUSR10P40B07RO | Open | 38.3 ± 1.0 | NA | 50 x 50 | N - Rx Only |
| Multicomp | MCUSR16A39S12RO | Open | 39 ± 1.0 | NA | 50 x 50 | N - Rx Only |
| Multicomp | MCUSR16P40B12RO | Open | 39 ± 1.0 | NA | 50 x 50 | N - Rx Only |
| Multicomp | MCUSR18A40B12RS | Closed | 40 ± 1.0 | 160 | 80 x 80 | Y |
| Multicomp | MCUST10P40B07RO | Open | 40 ± 1.0 | TBD | 50 x 50 | N - Tx Only |
| Multicomp | MCUST16A40S12RO | Open | 40 ± 1.0 | TBD | 50 x 50 | N - Tx Only |
| Multicomp | MCUST16P40B12RO | Open | 40 ± 1.0 | TBD | 50 x 50 | N - Tx Only |
| Multicomp | SQ-40-R-10B | Open | 40 ± 1.0 | NA | 60 x 60 | N - Rx Only |
| Multicomp | SQ-40-T-10B | Open | 40 ± 1.0 | TBD | 60 x 60 | N - Tx Only |
| Murata | MA300D1-1 | Closed | 300 | 50 | 5 x 5 | Y |
| Murata | MA40H1S-R | Open | 40 | 7.2 (square) | 45 x 45 | Y |
| Murata | MA40S4R | Open | 40 | NA | 80 x 80 | N - Rx Only |
| Murata | MA40S4S | Open | 40 | 20 (sqr) | 80 x80 | N - Tx Only |
| Murata | MA58MF14-7N | Closed | 58.5 ± 1.5 | 120 | 80 x 35 | Y |
| Prowave | 043SR750 | Closed | 43 ± 4.0 | 1500 | 10 x 10 | Y |
| Prowave | 080SR365 | Closed | 80 ± 5.0 | 700 | 9 x 9 | Y |
| Prowave | 200GE180 | Closed | 200 ± 10.0 | 50 | 10 x 10 | Y |
| Prowave | 200LM450 | Closed | 200 ± 10.0 | 50 Watts | 20 x 20 | Y |
| Prowave | 235SR130 | Closed | 235 ± 10.0 | 80 | 9 x 9 | Y |
| Prowave | 320SR093 | Closed | 320 | 50 | 11.5 x 11.5 | Y |
| Prowave | 320SR093 | Closed | 320 ± 10.0 | 50 | 11 x 11 | Y |
| Prowave | 328ER250 | Closed | 32.8 ± 1.0 | NA | 33 x 33 | N - Rx Only |
| Prowave | 328ET250 | Closed | 32.8 ± 1.0 | 20 Vrms | 33 x 33 | N - Tx Only |
| Prowave | 328SR160 | Open | 32.8 ± 1.0 | NA | 100 x 100 | N - Rx Only |
| Prowave | 328SR180 | Open | 32.8 ± 1.0 | NA | 45 x 45 | N - Rx Only |
| Prowave | 328ST160 | Open | 32.8 ± 1.0 | 20 Vrms | 100 x 100 | N - Tx Only |
| Prowave | 328ST180 | Open | 32.8 ± 1.0 | 20 Vrms | 45 x 45 | N - Tx Only |
| Prowave | 400EP125 | Closed | 40 ± 1.0 | 100 | 108 x 108 | Y |
| Prowave | 400EP14D | Closed | 40 ± 1.0 | 100 | 135 x 85 | Y |
| Prowave | 400EP18A | Closed | 40 ± 1.0 | 100 | 85 x 85 | Y |
| Prowave | 400EP18D | Closed | 40 ± 1.0 | 100 | 135 x 75 | Y |
| Prowave | 400EP250 | Closed | 40 ± 1.0 | 100 | 23 x 23 | Y |
| Prowave | 400ER080 | Closed | 40 ± 3.0 | NA | 125 x 125 | N - Rx Only |
| Prowave | 400ER180 | Closed | 40 ± 1.0 | NA | 30 x 30 | N - Rx Only |
| Prowave | 400ER18S | Closed | 40 ± 1.0 | NA | 35 x 35 | N - Rx Only |
| Prowave | 400ER250 | Closed | 40 ± 1.0 | NA | 30 x 30 | N - Rx Only |
| Prowave | 400ET080 | Closed | 40 ± 3.0 | 15 Vrms | 125 x 125 | N - Tx Only |
| Prowave | 400ET180 | Closed | 40 ± 1.0 | 15 Vrms | 30 x 30 | N - Tx Only |
| Prowave | 400ET18S | Closed | 40 ± 1.0 | 15 Vrms | 35 x 35 | N - Tx Only |
| Prowave | 400ET250 | Closed | 40 ± 1.0 | 20 Vrms | 30 x 30 | N - Tx Only |
| Prowave | 400PT120 | Open | 40 ± 1.0 | 20 Vrms | 85 x 85 | Y |
| Prowave | 400PT160 | Open | 40 ± 1.0 | 20 Vrms | 40 x 40 | Y |
| Prowave | 400SR100 | Open | 40 ± 1.0 | NA | 72 x 72 | N - Rx Only |
| Prowave | 400SR120 | Open | 40 ± 1.0 | NA | 85 x 85 | N - Rx Only |
| Prowave | 400SR160 | Open | 40 ± 1.0 | NA | 55 x 55 | N - Rx Only |
| Prowave | 400ST100 | Open | 40 ± 1.0 | 10 Vrms | 72 x 72 | N - Tx Only |
| Prowave | 400ST120 | Open | 40 ± 1.0 | 20 Vrms | 85 x 85 | N - Tx Only |
| Prowave | 400ST160 | Open | 40 ± 1.0 | 20 Vrms | 55 x 55 | N - Tx Only |
| Prowave | 480EP900 | Closed | 48 ± 1.0 | 100 | 19 x 38 | Y |
| Prowave | 500ES290 | Open | 50 ± 1.0 | 300 | 13 x 13 | Y |
| Prowave | 500ES430 | Open | 50 ± 1.0 | 300 | 13 x 13 | Y |
| Prowave | 500MB120 | Closed | 50 ± 1.0 | 20 Vrms | 30 x 30 | Y |
| PUI Audio | UR-1240K-TT-R | Open | 40 ± 1.0 | NA | 70 x 70 | N - Rx Only |
| PUI Audio | UR-1640K-TT-2-R | Open | 40 ± 1.0 | NA | 80 x 80 | N - Rx Only |
| PUI Audio | UT-1240K-TT-R | Open | 40 ± 1.0 | 30 Vrms | 70 x 70 | N - Tx Only |
| PUI Audio | UT-1640K-TT-2-R | Open | 40 ± 1.0 | 20 Vrms | 80 x 80 | N - Tx Only |
| PUI Audio | UTR-1440K-TT-R | Closed | 40 ± 0.7 | 140 | 70 x 70 | Y |
| SensorTec | ST-203 | Closed | 40 | 100 | 90 x 90 | Y |
| SensorTec | ST-205 | Closed | 40 | 100 | 100 x 50 | Y |
| SensorTec | ST-206 | Closed | 40 | 100 | 50 x 50 | Y |
| SensorTec | ST-207 | Closed | 40 | 100 | 100 x 50 | Y |
| SensorTec | ST-208 | Closed | 48 | 100 | 100 x 40 | Y |
| SensorTec | ST-209 | Closed | 58 | 100 | 80 x 40 | Y |
| SensorTec | ST-210 | Closed | 40 | 100 | 120 x 50 | Y |
| SensorTec | ST-212 | Closed | 58 | 100 | 100 x 40 | Y |
| SensorTec | ST-216 | Closed | 58 | 100 | 100 x 40 | Y |
| SensorTec | ST-301 | Closed | 70 | 140 | 8 x 8 | Y |
| SensorTec | ST-302 | Closed | 200 | 120 | 8 x 8 | Y |
| SensorTec | ST-401C | Closed | 30 | 200 | 10 x 10 | Y |
| SensorTec | ST-402C | Closed | 43 | 200 | 10 x 10 | Y |
| SensorTec | ST-403C | Closed | 70 | 200 | 10 x 10 | Y |
| SensorTec | ST-501 T/R | Open | 40 | 20 Vrms | 55 x 55 | Y |
| SensorTec | ST-502 T/R | Open | 40 | 20 Vrms | 72 x 75 | Y |
| Steminc | SMATR10H40X80 | Closed | 40 | 120 | 80 x 80 | Y |
| Steminc | SMATR10H60X80 | Closed | 60 | 140 | 80 x 80 | Y |
| Steminc | SMATR15F45H5 | Closed | 45 | 160 | TBD | Y |
| Steminc | SMATR18H40XLK3 | Closed | 40 | 140 | 120 x 50 | Y |
| Steminc | SMATR200H19XDA | Closed | 200 ± 4.0 | 500 | 14 x 14 | Y |
| Steminc | SMATR300H19XDA | Closed | 300 ± 5.0 | 400 | 10 x 10 | Y |
| Steminc | SMATR400H99XDA | Closed | 400 ± 5.0 | 500 | TBD | Y |
| Steminc | SMUTF40TR15A | Closed | 40 | 160 | 100 x 100 | Y |
| Steminc | SMUTF40TR15B | Closed | 40 | 160 | 50 x 100 | Y |
| Steminc | SMUTF40TR18A | Closed | 40 | 160 | 75 x 75 | Y |
| Transformers for Air-Coupled Ultrasonic Transducers | ||||||
| Manufactuer | Part Number | Type | Turns Ratio | Secondary Inductance (mH) | Specifications Frequency (kHz) | Recommended Transducer Frequency (kHz) |
| Coilcraft | WA8351-AL | Fixed | 1 : 1 : 8.42 | 3.0 ± 10% | TBD | 30 to 80 |
| Mitsumi | K5-R4 | Tunable | 1 : 1 : 10 | 2.2 ± 5% | 10 to 100 | 30 to 80 |
| Murata-Toko | N1342DEA-0008BQE=P3 | Tunable | 1 : 1 : 10 | 2.5 ± 5% | 252 | 30 to 80 |
| Prowave | K4000001 (33 69) | Tunable | 1 : 10 | 10.6 ± 6% | 40 | 40 |
| Prowave | K4000002 (33 70) | Tunable | 1 : 10 | 5.3 ± 6% | 40 | 40 |
| SensComp | 619391SMTLF | Fixed | TBD | 22 ± 10% | 55 | TBD |
| TDK-EPCOS | B78416A2232A003 | Fixed | 1 : 1 : 8.42 | 3.0 ± 10% | 52 | 30 to 80 |
| TDK-EPCOS | B78416A2386A003 | Fixed | 1 : 1 : 9 | 0.2 ± 8% | 300 | 180 to 480 |
| Wurth Elektronik | 750316928 | Fixed | 1 : 1 : 9 | 0.239 ± 8% | 300 | 180 to 480 |
↧
↧
AWR1243: Synthesizer Sweep Bandwidth
Part Number:AWR1243
Hi,
I understand that there are separate VCOs covering 76-77 GHz and 77-81 GHz.
In this scenario, is it possible to sweep from 76-78 GHz even though this sweep bandwidth would transition between two different VCOs without introducing any glitches in the chirp ?
Thank you,
RJ
↧
PGA411Q1EVM: Mounting Hole coordinates
Part Number:PGA411Q1EVM
Hello Team,
I have a customer requesting the XY coordinates for the EVM. Is this information available? Thank you.
Regards,
Ed
↧
DP83849IF: How do I configure a DP83849IF to interface for a copper ethernet connection to a fiber one.
Part Number:DP83849IF
Hello,
I am working a a redesign that uses a Lantronix Wi-PORT NR that takes a UART input and creates a 100BASE-TX copper ethernet connection. These copper ethernet signals are then routed to/from a Microlinear ML6652EM IC that takes wired Ethernet signaling data from a Lantronix WIPORT-NR unit and converts it to fiber based Ethernet through an Avago AFBR-5103AZ. I know that the Avago part was replaced by an AFBR-5803AZ but I cannot find any alternative for the ML6652EM. This circuitry has to be redesigned with currently available parts. Can the DP83849IF IC be wird in such a way to replace the ML6652EM device without using the MAC interface? Or if someone out there has a single and or dual IC solution that would convert either wired Ethernet into a fiber based Ethernet or maybe even something that would take a UART serial data stream (RS-232 TTL Level) or an SPI data interface and be able to convert that into a fiber based Ethernet signaling that would directly interface into a AFBR-5803AZ.
Thanks in advance for your help.
Wes
↧
↧
LMH6551: OP AMP Draw too Much Current
Part Number:LMH6551
Hi,
In my new design, the op-amps LMH6551 draw too much current from positive and negative supply.
Here is the schematic of the circuit. (There is 100nF between each VCP pin and GND)
1. First, I couldn't see any output signal, it was always zero.
2. Then, I decrease the gain resistors. Finally, I see output signal at output with a gain value. But opamp continue to draw too much current.
For you information, there is 20 opamp on board. They draw 2A per two supply.
Do you have any idea what causes this problem?
Thank you for your help.
↧
TPS65910: RTC without external oscillator / crystal?
Part Number:TPS65910
When using the internal RC oscillator, the RTC in the PMIC appears to loose 1-2 seconds every few minutes; The output frequency is 32.0kHz as expected per the datasheet.
After installing the 32.786kHz external crystal, and clearing the CK32K_CTRL bit, the time is spot on.
After reading the datasheet and forums, can I get a definitive answer to:
Is there a way to run the RTC off the internal oscillator without gross inaccuracies?
Is there a way to base it on the 32.0kHz internally generated clock?
Does it REQUIRE a 32.786kHz external crystal in order to be of any usefulness?
Thanks,
--Luke Suchocki
↧
TPS65912: Unable to program PMIC when connections change.
Part Number:TPS65912
Please consider these 2 scenarios:
1)
- EN1_DCDC1_SEL pin connected to an external wire for testing purposes but, for this particular case, no signal is inputted.
- INT1 is also connected to an external wire for testing purposes but, for this particular case, no signal is inputted.
- EN2/3/4_DCDC2/3/4_SEL are left floating.
- CONFIG1 and CONFIG2 are set to LOW and HIGH, respectively.
- SLEEP pin is grounded.
- PWRHOLD set to HIGH.
- nRESPWRON is floating.
Based on this configuration, I'm able to program the registers of LDO6, LDO7 and LDO8 and set their voltages to whatever I want.
2)
- ENx_DCDCx_SEL are all grounded.
- INT1 is floating.
- LDO6/7/8_EN1/2/3/4 (on ENx_SETx registers) bits are set to 0 so the pins have no effect on enabling and disabling the LDOs.
- SLEEP pin is grounded and the DEVCTRL2:SLEEP_POL bit is set to 0 for an active high.
- CONFIG1 and CONFIG2 are set to LOW and HIGH, respectively.
- PWRHOLD set to HIGH.
- nRESPWRON is also floating.
With this set up however I am unable to program LDO6, LDO7 and LDO8...Any idea why?
Thank you!
↧
RTOS/66AK2H12: c++ try()/catch()
↧
↧
DP83822H: TM4C129XNCZAD and DP83822 transformerless configuration unreliable
Part Number:DP83822H
Hello all,
I have implemented a DP83822 tm4c129x combination and connected the DP83822 in rmii mode to its mac. The tiva is using a stock lwip config from tivaware and we have coded the configuration to be force 10 full duplex and commented any autonegotiation register calls. The links are unreliable at times. Autonegotiation has never worked and forcing the speed seems to be the only way to connect. I have followed TI's app note on transformerless operation and although the app note suggests that the devices will perform in 100TX mode, we have never actually been able to achieve a 100TX link.
In the schematic, I have 12 DP83822 phys connected to my fpga. The phys have a 51 ohm pullup on the pairs followed by a series 0.1uF capacitor. They connect to the tiva with another 51 ohm pullup on the pairs. The link length is very short - on the order of about a couple inches from phy to tiva.
I have tried various combinations of register settings and forcing vs autonegotiation and was wondering if the hardware configuration is possibly an issue or if there is a preffered method to connect them. One caveat is that the tx pairs are connected to tx on the other side and rx as well. This requires that one of the phys be configured to swap the pairs internally.
Thank you in advance.
-Joe
↧
RI-CTL-MB2B: TIRIS Reader Manager (TRM) software - available for download?
Part Number:RI-CTL-MB2B
I have an old board that failed and I need to program the spare one. Is the software TIRIS Reader Manager (TRM) still available for download? This software is mentioned in the user manual for the board.
Thanks.
Constantin
↧
BQ20Z80A-V110: absolute capacity and remaining capacity stop decrementing at ~20%SOC
Part Number:BQ20Z80A-V110
We are having trouble with the gas gauging accuracy on the BQ20Z80 V1.10. It appears that on discharge that the absolute capacity and relative capacity both stop decrementing at ~20% SOC even though I can still get that ~20% out of the pack before the BMS opens the discharge FETs. It will then recalibrate and adjust to 0% after resting. We have tried a couple times to follow the SLA334B to help with the accuracy issues and make a golden file. The trouble is that the 3 calibration cycles do not appear to be helping the issue. We can see that after the 2 hour rest once the pack is charged and the 5 hour rest once the pack is discharge that the recalibration occurs; however it continually stops decrementing at ~20% on relative capacity and adjusting later. Something else we noticed is that the relative capacity ~20% is right around 3.48-3.5V/cell. Another data point is the QMAX values appear to be updating with each cycle as they are suppose to when making a golden file.
↧
RTOS/TM4C129CNCZAD: After waking up from hibernation and performing soft reset, the code does not start from Bootloader.
Part Number:TM4C129CNCZAD
Tool/software:TI-RTOS
Hi all,
I hope you are doing fine.
I am working with TM4C129XNCZAD hibernation mode and am having issues with soft reset after waking up from hibernation. I have listed the details below. Please have a look at these.
In our project, we are using a Bootloader based on TI RTOS and it is assigned ROM adresses from 0x00000000 to 0x027FFF. The main application code, also based on TI RTOS, is present on ROM address from 0x00029000 to 0x000FAFFF. In main application code, the shutdown code puts MCU in hibernation mode and tamper events 0(PM7) and 1(PM6) are configured to wake the MCU from hibernation. After waking up from hibernation, in tamper event handler i am clearing the tamer events and after disabling the tamper module, i do a soft reset. I having problems waking up from hibernation and these are detailed below.
(i) When using bootloader, after waking up from hibernation the control does not return to bootloader. If , in shutdown function, instead of putting MCU to hibernation, i do a soft reset then the code starts execution from bootloader.
(ii )If i don't use the bootloader and configure my main application to start from 0x00000000, it works fine after waking up from hibernation.
If anyone has experience with using hibernation, please let me know what am i missing here that is causing issues with hibernation.
Thanks,
Muhammad Shuaib
↧
↧
RTOS/66AK2H12: Compiling C++
Part Number:66AK2H12
Tool/software:TI-RTOS
I just posted a question regarding c++ try/catch but I guess the bugger question is guidelines on compiling/linking c++ classes in general.
I am trying to port some existing c++ code and that code using new and delete as well as calls to the std library, for example std::copy, std:runtime_error(), etc.
The SYS/BIOS UG says: "The functions new and delete are the C++ operators for dynamic memory allocation and deallocation. For TI targets, these operators use malloc() and free()." but I can't seem to get them to link (undefined references).
My application is to run on a ARM15 core.
Thanks, Mike
↧
TS5V330C: part use for non-video applications
Part Number:TS5V330C
Hi,
I would like to know if we can use this switch generically for analog applications.
I've been using the NXP NX5DV330PW, and observed strange behavior. This TI part is listed as a direct replacement for the NXP part on Digi-key.
My problem with the NXP (hopefully not the TI part) is that although the RDON is supposed to be 10 Ohms, the voltage difference between input/output is 1V. I input a 5V pulse and observe a 4V pulse at the output with a scope. the load is an OP-Amp. (high impedance).
We want to use the chip to switch TTL or RS422 pulses, and also some analog signals in other applications.
The pules are about 100uS, the frequency up to 200Hz.
We power the IC with 5V, and the signals trough the input/outputs are up to 5V.
we do not toggle the switch during operation, we select with a jumper which switch to use (S1 or S2).
Thanks,
Victor
↧
RTOS/CC2640R2F: How to configure an interrupt
Part Number:CC2640R2F
Tool/software:TI-RTOS
Hello,
I started with a Simple BLE Peripheral project and I'm trying to add an interrupt that when triggered would call a function that would talk to EEPROM using I2C. The interrupt fired and generated an event however for some reason I2C writing/reading stopped working. I also noticed BLE stopped advertising after an interrupt fired.
Is my interrupt not setup correctly?
This is what I did:
// EEPROM IRQ pin configuration table
static PIN_Config SBP_configTable[] =
{
EEPROM_WIP_IRQ | PIN_INPUT_EN | PIN_PULLUP,
PIN_TERMINATE
};hSbpPins = PIN_open(&sbpPins, SBP_configTable); // Register ISR PIN_registerIntCb(hSbpPins, EEPROM_WIP_HwiFxn); // Configure interrupt PIN_setConfig(hSbpPins, PIN_BM_IRQ, EEPROM_WIP_IRQ | PIN_IRQ_NEGEDGE); // Enable wakeup PIN_setConfig(hSbpPins, PINCC26XX_BM_WAKEUP, EEPROM_WIP_IRQ|PINCC26XX_WAKEUP_NEGEDGE);
static void SimpleBLEPeripheral_processAppMsg(sbpEvt_t *pMsg)
{
switch (pMsg->hdr.event)
{
case SBP_STATE_CHANGE_EVT:
SimpleBLEPeripheral_processStateChangeEvt((gaprole_States_t)pMsg->
hdr.state);
break;
case SBP_CHAR_CHANGE_EVT:
SimpleBLEPeripheral_processCharValueChangeEvt(pMsg->hdr.state);
break;
case SBP_NFC_IRQ_EVT: // this is my interrupt event
nfcWipInterrupt(); // NFC WIP interrupt
break;
default:
// Do nothing.
break;
}
}
↧
What's the best evaluation board to start a Bluetooth/WiFi project?
Hi,
I have a project to pair a cell phone to a MCU through Bluetooth and am looking for a Blue tooth evaluation module. Is CC2640R2F the best option for beginners? Do you think if it's better to have a WiFi+Bluetooth board instead of only Bluetooth board? Can I use Simulink to program the board?
Thanks,
--Kash
↧
↧
CCS/CC3100BOOST: Trouble with example mqtt
Part Number:CC3100BOOST
Tool/software: Code Composer Studio
hello ,
i am working with the cc3100boost , i want to run a client for mqtt , i was based in the examples in SDK folder cc3100 , but i have problem with the archives mqtt.a and osi_lib.lib i don't found , and cant run the example , where can a find the librarys , or what i am doing wrong?? ,thanks .
↧
AM1808: EMAC HOSTPEND interrupt recovery
Part Number:AM1808
Hi,
I wanted to confirm that the only way to recover from a HOSTPEND interrupt, which are triggered by errors in packet buffer descriptors, is to do a HW WARM RESET of the chip. Is this correct?
The TRM states:
18.2.14.2 Hardware Reset Considerations
When a hardware reset occurs, the EMAC peripheral has its register values reset and all the components
return to their default state. After the hardware reset, the EMAC needs to be initialized before being able
to resume its data transmission, as described in Section 29.2.19.
A hardware reset is the only means of recovering from the error interrupts (HOSTPEND), which are
triggered by errors in packet buffer descriptors. Before doing a hardware reset, you should inspect the
error codes in the MAC status register (MACSTATUS) that gives information about the type of software
error that needs to be corrected. For detailed information on error interrupts, see Section 18.2.16.1.4.
But I have seen some other threads where folks have tried to recover by having HOSTPEND masked and poll for the interrupt status. Then if HOSTPEND occurred, the approach was to reboot the network stack, which in turn executed the EMAC deinit() functions and then the init() functions. Has this been tested? Or is the only way to recover to do the HW WARM RESET?
Thanks,
--Gunter
↧
CC2564: Is Slow Clock Necessary?
Part Number:CC2564
Hello,
I have a customer design which replicates the BT-MSPAUDSINK-RD.
However, my customer was thinking about removing the 0 Ohm between the MSP430 and the CC2564 SLOW_CLK_IN.
Is this allowed? If not, why not?
Thank you for your help,
Louie
↧