The Kynix Blog - General electronic semiconductor

SummaryAs the development of socialty,basically a family will own one car even in the development country. In the future over-the-air updates keep them constantly up to date,and thus also secure.  In the future, car owners will be able to enhance their car’s security, intelligence, and performance without getting up from the sofa. In the future, updating their car’s software will be as simple as updating apps on their smartphones today. A swipe of the smartphone will be enough to automatically update vehicle software or to download new functions directly from the cloud – without any need to visit the repair shop.    Situation AnalysisMore electronics, more functions, more software: the car is turning into a smartphone on wheels. Keeping vehicle software up to date is thus becoming increasingly important. New functions can provide extra convenience, even after the vehicle has been bought. Over-the-air software updates will therefore soon be a standard feature.Today’s vehicles feature as many as 100 control units. Even compact cars have between 30 and 50. Their software governs nearly every function in the vehicle. In addition, more and more vehicles are now connected – with the internet, other cars, and the infrastructure. This means a greater risk of weak links in vehicle software, as well as of manipulation. In this context, software updates over the cloud offer a solution that keeps cars constantly up to date, and thus also secure. In addition, the cloud updates mean that ever more functions can be added, with ever greater scope.If the necessary hardware is already installed, a new software function can be tried out and subsequently downloaded. In this way, lane-keeping or park-assist functions can be added, for example. And it is not just drivers that benefit from over-the-air software updates: in 2015, 15 percent of recalls in the automotive industry in the U.S. had to do with software errors. Four years previously, this figure was only 5 percent, according to a U.S. study based on data from the National Highway Traffic Safety Association (NHTSA). For automakers and their customers alike, such repair-shop visits are a huge waste of time and money, and online updates can significantly reduce this.  Over-the-air Software UpdateThe over-the-air software updates work priciple is secure,fast and simple. On the driver's smartphone or the car’s infotainment system, the online security updates are started and any new functions that need to be downloaded are selected. This information is sent to the cloud, which acts like a kind of app store, holding the updates in readiness and starting the process of downloading software to the vehicle. The data can either be downloaded in the background while the car is moving, or overnight when it is parked in its garage. As soon as the vehicle is in a secure condition (once it has parked, for example), the software updates are installed on the appropriate control units, where they are immediately activated. Security and the smooth interaction of automotive electronics, cloud, and software are decisive for an over-the-air update. Data security is ensured by the latest encryption technologies. A complex security architecture with end-to-end encryption protects the data transmission against unauthorized access. At the car-cloud interfaces, secure protocols and filters act like a firewall to ward off any hacking attempts. To ensure that an over-the-air update is not just secure, but also fast and reliable, fast update technologies such as delta and compression mechanisms are used. These accelerate the update process and reduce cost, since the data volume for the transmission remains low. One further security measure is to transmit the updates in sequences. If problems occur, the update process can be stopped and adjusted. Article resources: BoschArticle edited by kynix 

SummaryPublished in the Joural Nature Materials in Nov.13,2017,reaearchers from Princeton University,the Georgia Institute of Technology and Humboldt Uniersity in Berlin is pointing the way to possibly more widespread use of organic electronics. Their research focuses on organic semiconductors,a class of materials prized for their applications in emerging technologies such as flexible electronics, solar energy conversion, and high-quality color displays for smartphones and televisions. In the short term, the advance should particularly help with organic light-emitting diodes that operate at high energy to emit colors such as green and blue.  Body“Organic semiconductors are ideal materials for the fabrication of mechanically flexible devices with energy-saving low-temperature processes,” said Xin Lin, a doctoral student in electrical engineering at Princeton and the lead author. “One of their major disadvantages has been their relatively poor electrical conductivity. In some applications, this can lead to difficulties and inefficient devices. We are working on new ways to improve the electrical properties of these organic semiconductors.” Semiconductors, typically made of silicon, are the foundation of modern electronics because engineers can take advantage of their unique properties to control electrical currents. Among many applications, semiconductor devices are used for computing, signal amplification and switching( signal switches ). They are used in energy-saving devices such as light-emitting diodes and devices that convert energy such as solar cells. In the doping process used to make semiconductors their chemical makeup is modified by adding a small amount of chemicals or impurities. By carefully choosing the type and amount of dopant, researchers are able to alter the electronic structure and electrical behaviour of the semiconductor in a number of ways. As the article shows,researchers have developed an approach for greatly increasing the conductivity of organic semiconductors,which are formed of carbon-based molecules rather than silicon atoms. The dopant, a ruthenium-containing compound, is a reducing agent, which means it adds electrons to the organic semiconductor as part of the doping process. The addition of the electrons is the key to increasing the semiconductor’s conductivity. The compound belongs to a newly introduced class of dopants called dimeric organometallic dopants. Unlike many other powerful reducing agents, these dopants are stable when exposed to air but still work as strong electron donors both in solution and solid state. Seth Marder and Stephen Barlow from the Georgia Institute of Technology, who led the development of the new dopant, called the ruthenium compound a “hyper-reducing dopant.” They said it is unusual, not only in its combination of electron donation strength and air stability, but in its ability to work with a class of organic semiconductors that have previously been very difficult to dope. In studies conducted at Princeton, the researchers found that the new dopant increased the conductivity of these semiconductors about a million times. The ruthenium compound is a dimer, which means it consists of two identical molecules, or monomers, connected by a chemical bond. As is, the compound is relatively stable and, when added to these difficult-to-dope semiconductors, it does not react and remains in its equilibrium state. That posed a problem because to increase the conductivity of the organic semiconductor, the ruthenium dimer needs to react with the semiconductor it and then split apart. The researchers looked for different ways to break up the ruthenium dimer and activate the doping, eventually they added energy by irradiating with ultraviolet light, which effectively excited the molecules in the semiconductor and initiated the reaction. Under exposure to the light, the dimers split into monomers, and the conductivity rose. "Once the light is turned off, one might expect the reverse reaction to occur" and the increased conductivity to disappear, Marder said. "However, this is not the case." The researchers found that the ruthenium monomers remained isolated in the semiconductor even though thermodynamics should return the molecules to their original configuration as dimers. The team's hypothesis is that the monomers are scattered in the semiconductor in such a way that it is very difficult for them to return to their original configuration and re-form the ruthenium dimer. They are, according to the team “kinetically trapped." The researchers also discovered that doping was continuously re-activated by the light produced by the device. The light activates the system more, which leads to more light production and more activation until the system is fully activated, Marder said. "This alone is a novel and surprising observation." The work was supported in part by the National Science Foundation and the U.S. Department of Energy. Article edited by kynix   

DescriptionFor everyone,electrical energy is essential. We always trying to get unlimited electrical energy without spending money. Now kynix share a simple design proposed as small wind turbine for home use or low power usage,it requires low initial cost and gives best return in terms of electrical energy. Use the following small wind turbine circuit and setup to charge laptop,to charge electronic gadgets or to electronic appliances in home and outstations.  NoteBefore we start,we should emphasis that we should note:* High voltage caution! This Circuit Involves in operating High voltage handle with extreme care.* Handle the Wind Turbine Generator and Rotor blade as per the Instructions given by manufacturer.  Windmill Generator DesignSmall 12V wind turbine generator is capable of producing alternate energy through wind, the Bridge rectifier and controller rectifies the energy came from wind turbine generator and regulator-battery charger circuit helps 12V/4.5Ah SLA battery to get charging, then Step-up inverter circuit produce high voltage AC enough to operate home appliances.  Schematic of Wind Turbine Generator is as following.  WorkingThere are five stages:  1. 12V Wind turbine generator/Bridge Rectifier Circuit  2. Regulator / Battery charger circuit  3. Inverter circuit using CD4047  4. mosFET Drivers  5. Output Stage 12V Wind Turbine Generator12 Volt wind turbine or windmill available with different watts range, choose depends on your requirement. Bridge RectifierWe know the bridge rectifier converts AC supply into DC and here we used 1N4007 diode as a bridge rectifier element, it converts the energy from wind turbine into Direct Current (DC) supply. Regulator / Battery ChargerThe LM317 adjustable three terminal Positive voltage Regulator used here and it can give output voltage range from 1.25 V to 37 V with more than 1.5A current rating. final output from the regulator is given to 12/4.5Ah SLA Battery, this Battery provides DC bias to the inverter circuit. Regulator LM317 output voltage Vout can be obtained asVout = 1.25V *(R2/R1+1) R2 => R2+VR1 for given inverter circuit.Inverter Circuit using IC CD4047 (Switching Pulse Oscillator) Monostable / Astable multivibrator  CD4047 used here to produce switching pulse, This IC works in low power and available in 14 pin Dual in line package. It provides full Oscillation output F at Pin 13, 1/2 of oscillation at Pin 10 as Q and Pin 11 as Q’. each output pin gives 50% duty cycle.f = 1/8.8RCHere R => R4+VR2 and C=> C3. by using this formula we can obtain frequency output at pin 13. For pin 10 and 11 the formula changes as f=1/4.4RC. MosFET driversIRF540 N Channel power mosfet from vishay siliconix used as a switching drivers for this inverter circuit. It gives fast switching, and have high operating temperature characteristics (175ºC). Output StageMain part of wind turbine generator is output stage, here transformer X1 is used in reverse with specifications as 230V primary, 9V-0-9V / 1.5A secondary winding center tapped transformer. MOV (Metal oxide Varistor) protects electronic device connected at output. Wind turbine generator output voltage is directly fed into LM317 positive Regulator circuit and it is adjusted to give 12 volt output and Battery connected to this bias through (3A, 50V) Schottky diode. The CD4047 IC is connected and configured as Astable multivibrator, When we turn ON SPST switch this circuit starts oscillation. Output Q and Q’ are directly fed into switching power mosfet IRF540 & drives X1 transformer secondary winding, here the current flow occurs particular duration and not for particular duration. So varying electromagnet induced and primary winding coil produce EMF, hence we get Alternating current output. Depends on the count of winding and switching frequency output Voltage/Frequency get varied. 

DescriptionIt's not weird to discover that applications are becoming more complex,with connectivity just one of the drivers. And,as it become more complex.the number of sensors grows,as does the need for more capable user interfaces. At the same time,algoriths need more processing power,wireless stacks mandate larger memories and power budgets are shrinking.In order to coping with the growing list of demands, a great number of leading MCU manufacturers have recently launched Micro Controller Unit built around the ARM Cortex-M4 core. BodyThe M3 is general purpse and the M0+is low cost but the M4 is a more capable core in general if look at the Cortex range. Oivind Loe,a senior strategic marketing manager with Sillicon Laboratories said. Microchip's product marketing manager--Anand Rangara commented:“Something that sat around without the need to communicate now needs connectivity. When that happens, you need more flash and RAM, as well as graphics capability and perhaps the ability to support a touch interface. All this has to be offered at good power/performance and an attractive price.”  'Industrial Strength' MCUsSilicon Labs has expanded its EFM32 Gecko portfolio with what it calls ‘industrial strength’ MCUs. It says the EFM32GG11 Giant Gecko MCU family offers the ‘most advanced’ feature set available in the low-power MCU market.Loe noted that MCU development isn’t just about power. “It’s also about executing tasks efficiently. A simple program with a few clocks will run efficiently on an M0+ core. But if the workload is larger, the M4 core has some special instructions that can allow it to use less energy than the M0+ and more efficiently than some larger cores – and that's crucial for a range of application.” GG11 Geckos offer up to 2Mbyte of flash and 512kbyte of RAM to accommodate more code and comms stacks, such as a 10/100 Ethernet MAC and a dual CAN interface. Looking to meet power budgets, the parts boast an active power consumption of 77μA/MHz, while drawing 1.6μA in deep sleep mode. FPU to Increase System EffiencyMicrochip’s SAM D5x/E5x MCUs also take advantage of the Cortex-M4’s floating point unit (FPU) to increase system efficiency. Running at up to 120MHz, the D5x and E5x MCUs come with up to 1Mbyte of dual-panel flash and up to 256kbyte of SRAM. Rangarajan noted: “We’ve listened to our customers, so we’ve included more connectivity in these MCUs. But it's not just about adding memory , it’s also about more performance and the ability to provide more flexible peripherals, interfaces and connectivity options.” Meanwhile,he  pointed out that the original SAM D MCUs – developed by Atmel prior to its acquisition by Microchip – were based on the Cortex-M0+. “But we’ve always wanted to take the product line to the next level of performance. This allows Microchip to address a broader range of consumer and industrial automation applications.” Limited the Clock RateBucking the trend to a certain extent, both Silicon Labs and Microchip have limited the clock rate in their latest MCUs. Giant Geckos, for example, have a maximum clock of 72MHz. “These products are focused on energy efficiency,” Loe claimed. “If you build an MCU to run at 200MHz, for example, then each clock cycle will consume more energy than in an MCU running at 72MHz. A lot of MCUs will be used in battery powered apps, so we need to be energy efficient and to enable the CPU to sleep a lot.” Rangarajan agreed that clock rate is not always the primary factor when it comes to developing MCU portfolios. “We hear our customers saying don’t give me faster clock rates, make sure the MCUs meet my requirements. An app that runs from a battery requires a power efficient MCU. If you want a fast MCU, then you have to make trade offs.” In Loe’s views, MCU selection is all about the ability to perform certain tasks at a particular power efficiency. “That is always going to involve trade offs, but an M4 based MCU will generally be good for embedded applications with challenging energy consumption requirements.” Adopt the Concept of Smart PeripheralsBoth companies have adopted the concept of smart peripherals in their recent products. Loe explained: “Twenty years ago, most MCUs saw the CPU doing everything. That took a lot of CPU cycles, which meant you couldn’t do as much as you might have liked.“Today, most apps will take advantage of DMA, which offloads the CPU. In turn, this allows the CPU to do more.” Rangarajan said Microchip provides what he called ‘sleepwalking’ peripherals. “If there’s a requirement for them to do small numbers of transactions, this can be done without waking the CPU.” On the other hand,Sillicon Loe Noted that It’s all about when you have to wake up the M4 core. We’re trying to allow it to sleep for as much as possible. More than half of the peripherals in a Giant Gecko can run autonomously in deep sleep mode. Both Companies are Keen to Highlight Their Provision Silicon Labs has launched a starter kit to support Giant Gecko based application development(following picture) With this approach, a Giant Gecko’s A/D converter can operate while the CPU is in deep sleep mode. “It can sample and use DMA to pull the data into RAM,” Loe continued.Loe highlighted a couple of aspects. “We have included a cyrotimer that runs in shut off; the lowest energy mode. It’s a simple timer that’s useful when you need the CPU to be asleep for minutes. there’s the Peripheral Reflex System, which allows peripherals to talk. For example, the real time clock could tell the A/D converter to take a sample. It gives a level of determinism which you don’t get from a CPU.  Microchip's Product brings better power efficiency How does an MCU developer differentiate their products from similar devices with an M4 core? Rangarajan pointed to the integration of a buck regulator. “This brings better power efficiency,” he claimed, “which means lower active power consumption; as little as 65µA/MHz. The parts also support flexible pin options.”“We’re offering the best integrated security features,” Rangarajan contended. “SAM Dx/Ex MCUs have crypto hardware acceleration – symmetrical and asymmetrical – and public key encryption, amongst other features. It’s something Microchip has taken to heart and has made sure it’s all in the MCU.“We’re offering the best integrated security features,” Rangarajan contended. “SAM Dx/Ex MCUs have crypto hardware acceleration – symmetrical and asymmetrical – and public key encryption, amongst other features. It’s something Microchip has taken to heart and has made sure it’s all in the MCU.  EndLoe pointed to the security management unit (SMU) as an ‘upgrade’ to the memory protection unit (MPU) associated with the M4’s core. “While the MPU allows you to segment memory into eight regions, the SMU takes that further. The MPU is restricted to eight regions, so there is limited granularity. The SMU allows you to selectively say which pieces of code can access each peripheral.” “All of this is important,” Rangarajan concluded, “as security will become standard in the next few years.” 

This is a good day because kynix will share an interesting project with you -- Luminous Halloween Costume !  Halloween is coming soon and I know at least that some of you are still procrastinationg you costume build. That's ok,I would share a fun and easy luminous Halloween costume that takes almost no time to buildstill impresses the pants off your friendsis appropriate for all ages So at first,we should prepare some components as follow: Knit Hat in Red, Green, Blue or White,etcBlack T-shirtElectrical TapeHot Glue Gun and GlueSoldering IronSolderQduino Mini Dev BoardWS2812 LED StripLiPo Battery Next,let's start to make it. The first step,I made the shirt which will represent the anode and cathode of the LED.Ake the electrical tape and cut it into two pieces. One should be about 2 inches shorter than your shirt, and the other about 4 inches shorter. On each piece cut one edge into a point. Then place them on the shirt parallel to each other, pointing downward from the collar. Set this aside. The second step, place the hat on whoever will be wearing the costume — or someone with a head similar in size. Fold up the bottom to make a small lip. Starting in the back, hot glue the LED strip to the hat, wrapping it around the hat from the bottom and moving up. Cut the LED strip when there is about 1 to 2 inches of hat left at the top. Next,take the hat off and count the number of LEDs on it. After that,we need to use the program provided below to program Qduino.You will need to make two small edits. First, update numPix variable to the number of LEDs on your hat. Then find the four colorWipe commands in the loop function. You will notice that I have included red, green, blue and white. Comment out the lines that are not the same color as your hat. If you have not already, you will need to install Adafruit’s Neopixel Library and the Qduino board into your board manager in Arduino. For more instructions on how to do this, please visit this Qduino Hookup Guide and our Arduino Library Installation tutorial. Upload your program using the code below://Melissa Felderman for SparkFun Electronics. Functions have been taken from the adafruit neopixel library example code.  #include <Adafruit_NeoPixel.h> #define PIN 2 int numPix=150; Adafruit_NeoPixel strip = Adafruit_NeoPixel(numPix, PIN, NEO_GRB + NEO_KHZ800); void setup() { strip.begin();  strip.show(); // Initialize all pixels to 'off'} void loop() {  // comment out all lines except the color you want on your hat.  colorWipe(strip.Color(255, 0, 0), 50); // Red  colorWipe(strip.Color(0, 255, 0), 50); // Green  colorWipe(strip.Color(0, 0, 255), 50); // Blue  colorWipe(strip.Color(0, 0, 0), 50); // White } // Fill the dots one after the other with a colorvoid colorWipe(uint32_t c, uint8_t wait) {  for(uint16_t i=0; i<strip.numPixels(); i++) {    strip.setPixelColor(i, c);    strip.show();    delay(wait);  }} Finally,Solder the LED strip’s leads to the Qduino. The DIN lead should go to D2 on the Qduino, VCC to VCC, and GND to GND. Pop in a LiPo battery to your Qduino and turn on to test.  Put on the black shirt and then the hat. Fold the bottom edge over again to make a lip. Hide the Qduino and LiPo inside, and then turn it on. Now you are a luminous human! 

Today,let's talk something about MSP430 interrupts and times.   About "Interrupt"   Do you know what is an "interrupt"? Interrupt is a signal that informs our MCU that a certain event has happened,causing the interruption of the normal flow of the main program and the execution of an "interrupt routine",that handles the event and takes a specified action. Interrupts are essential to avoid wasting the processor's valuable time in polling loops, waiting for external events (in fact they are used in Real-Time Operating Systems, RTOS).   In the MSP430 architecture, there are several types of interrupts: timer interrupts, port interrupts, ADC interrupts and so on. Each one of them needs to be enabled and configured to work, and there is a separate "service routine" for every interrupt.   About code  Now let's see how to use timer and port interrupts to flash some LEDs,we will keep the ADC interrupt for the next turorial. So,let's write some code!   #include "msp430g2231.h" void main(void){  WDTCTL = WDTPW + WDTHOLD;                 // Stop WDT   You should recognize those lines,we used them in the last tutorial to add the definition file for our MCU, declare the main function and stop the watchdog timer.  CCTL0 = CCIE;                             // CCR0 interrupt enabled  TACTL = TASSEL_2 + MC_1 + ID_3;           // SMCLK/8, upmode    CCR0 =  10000;                           // 12.5 Hz   Here's some interesting stuff. These lines configure the timer interrupt. We first enable it by setting the CCIE bit in the CCTL0 register. Then we set the clock for the timer module in the TimerA control register. If you have a look at the msp430g2231.h file, you can see that: TASSEL_2 selects the SMCLK (supplied by an internal DCO which runs at about 1 MHz); MC_1 selects the "UP mode", the timer counts up to the number stored in the CCR0 register; ID_3 selects an internal 8x divider for the supplied clock (in our case we have SMCLK/8).   Finally, we set the CCR0 register. We configured the TimerA module to count up to the number stored in this register before overflowing and triggering the interrupt. By setting it at 10000, we get an overflow-frequency of 12,5 Hz. In fact we have (SMCLK/8)/10000 = 12,5 . You may obtain several frequencies by changing this number (remember that the MSP430 has a 16-bit timer, so the value stored in the CCR0 register must not be higher than 65535), changing the dividers or adding an if-else block with a counter in the interrupt routine. Let's go ahead.    P1OUT &= 0x00;               // Shut down everything  P1DIR &= 0x00;                P1DIR |= BIT0 + BIT6;       // P1.0 and P1.6 pins output the rest are input  P1REN |= BIT3;                 // Enable internal pull-up/down resistors  P1OUT |= BIT3;                 //Select pull-up mode for P1.3     These lines should be familiar too, but there are some additions: firstly, we clear the PORT1 output and direction registers. Then we set the P1.0 and P1.6 pins as outputs and the rest as inputs. The last two lines enable the pull-up resistor on the switch (BIT3) so that the normal state (button not pressed) will be "1".  P1IE |= BIT3;                    // P1.3 interrupt enabled  P1IES |= BIT3;                  // P1.3 Hi/lo edge  P1IFG &= ~BIT3;               // P1.3 IFG cleared With these lines of code, we first tell the MCU to listen to the P1.3 pin for logic-state changes (effectively enabling the interrupt on that particular pin). Then we select the edge when the interrupt is raised (from High to Low or Low to High); remember that the button on the LaunchPad connects the input pin to GND when pushed and to VCC when not. For this reason we seletct Hi/Lo edge. Finally we clear the interrupt flag for that pin. The interrput flag register P1IFG reports when an interrupt is raised, and it should be cleared at the end of the interrupt service routine.  _BIS_SR(CPUOFF + GIE);        // Enter LPM0 w/ interrupt    while(1)                      //Loop forever, we do  everything with interrupts!  {}} With this line, as you can remember, we shut down the CPU to spare some power while keeping the interrupts enabled. Then we enter a loop to be sure the MCU does nothing else, as we do our job with interrupts. // Timer A0 interrupt service routine#pragma vector=TIMERA0_VECTOR__interrupt void Timer_A (void){  P1OUT ^= BIT0;                            // Toggle P1.0} This is the TimerA interrupt service routine. Every time the TimerA overflows, the code inserted in this routine (note the special declaration) is executed. As you can see we only toggle the P1.0 pin (red led on LaunchPad), then we return to normal execution. // Port 1 interrupt service routine#pragma vector=PORT1_VECTOR__interrupt void Port_1(void){       P1OUT ^= BIT6;                        // Toggle P1.6     P1IFG &=~BIT3;                        // P1.3 IFG cleared    } This is the Port1 interrupt service routine. Every time the we push the P1.3 button, the code inserted in this routine (note the special declaration) is executed. We toggle the P1.6 pin (greenled on LaunchPad), clear the P1.3 interrupt flag (very important) and then we return to normal execution. Compile and program the LaunchPad, you should see the red led blink, and the green led toggle when you press the P1.3 button. Here's the full code, enjoy! #include "msp430g2231.h"    void main(void){  WDTCTL = WDTPW + WDTHOLD;     // Stop WDT    CCTL0 = CCIE;                             // CCR0 interrupt enabled  TACTL = TASSEL_2 + MC_1 + ID_3;           // SMCLK/8, upmode  CCR0 =  10000;                     // 12.5 Hz    P1OUT &= 0x00;               // Shut down everything  P1DIR &= 0x00;                P1DIR |= BIT0 + BIT6;            // P1.0 and P1.6 pins output the rest are input  P1REN |= BIT3;                   // Enable internal pull-up/down resistors  P1OUT |= BIT3;                   //Select pull-up mode for P1.3  P1IE |= BIT3;                       // P1.3 interrupt enabled  P1IES |= BIT3;                     // P1.3 Hi/lo edge  P1IFG &= ~BIT3;                  // P1.3 IFG cleared  _BIS_SR(CPUOFF + GIE);          // Enter LPM0 w/ interrupt  while(1)                          //Loop forever, we work with interrupts!  {}}  // Timer A0 interrupt service routine #pragma vector=TIMERA0_VECTOR __interrupt void Timer_A (void) {     P1OUT ^= BIT0;                          // Toggle P1.0 } // Port 1 interrupt service routine#pragma vector=PORT1_VECTOR__interrupt void Port_1(void){       P1OUT ^= BIT6;                      // Toggle P1.6   P1IFG &= ~BIT3;                     // P1.3 IFG cleared }