Hvala. Hvala, da sem tukaj, da vse ideje, da vse koncepti, da vse izgleda. V tej konferenci vse objezovanje je digitalne transformacije. vse je pletforma za inovacije. Inovacije, ne v tehnologiji, ali v tehnologiji, kako smo izgledali tehnologije, kaj je za njihovo. Vsih krajci, kaj je Unija, v svoj krajci, kaj je tudi izgledali, v mali pravde, način, zelo zelo svobod, sama nekaj še stran, schon, na še sozit več. Tely biri mene ilič neče nekaj šezetom, kateri, ki stavimo, in je to da se zelo, pa, da bomo zelo, da nekaj nešto se spetne, nekaj nešto se spetne, nekaj nešte se spetne, ki se zelo, ki se zelo, ki se zelo, ki se zelo, inovojčen. Vsi nekaj neče povedali vse dnev, na ko je zelo povedal je govoril. Povedal je elektroniknih vsebov, povedal je zelo povedal na objevce na naši govorilji vsebov vsebov, technologies. We have developed the base solutions for the ICT environment for the e-government. These are electronic signatures, identities. We are working on the digital mail, save digital mail services, but these are only the fragments of the infrastructure. And actually this period, this time, now it changes the way how we look on our successes in this field because we are connecting all these fragments together. And it shows different, it creates different problems, because we are integrating our fragmented infrastructure now, integrating not only in our states, but we are trying to integrate it between our countries. And actually we are returning back to the problems which European Union have solved in a way of breaking the borders. We face the new borders. We face the borders within the country between the institutions. We face the new borders which appearing between our infrastructures between the countries. And we shall work to break the borders again. In parallel, we have found that connecting this fragmented infrastructure, we are creating a new environment, a digital environment, where we see the similarities with the physical environment. And this digital environment is working as an extent of the physical environment and also working as an environment as itself. And the governments and the states has a significant role in creating of this environment. We need to create new rules for this environment. We need to create the basic infrastructure for this environment, which is connected, where we do the same what we have done several decades ago when we broke the border between the countries which share the same culture, the same values in the European Union. And we need to work on the break of the borders again. Of course, these environments shall be connected between the countries. We shall work on the user experience of our citizens where they don't meet the obstacles, but they shouldn't meet. And of course this environment is the place for the innovation. The government is a platform for the European joint platform public infrastructure of the ICT infrastructure or the European Union digital environment. This digital environment is a significant base for developing of innovation, for developing of our startup companies. We can make also their life easier providing the services that we have created for our government benefit. In Latvia we are working now. We have found that we can share these resources, share these services that we have created. And of course it's not easy. This is connected with the cyber security as well. And we need to work in this direction very hard. But this environment as we provide the physical environment for our companies, for our citizens, the same environment shall be created in the digital infrastructure digital environment. Of course we have a lot of work to do there because we are facing the new paradigm. We are facing the virtual reality which is new dimension of our digital environment. We are facing the augmented reality where there is a huge place for innovation. And this is the development direction where government can create more advanced, more effective services for our citizens. We have found that government as a platform is not only the infrastructure, government as a platform is also the policy. The policy shall be more agile. This is a huge trend in ICT to do agile approach in the infrastructure and system development. But the same agile approach we can do in the making of our policies. As we are sharing our experiences, I want to share the experience of Latvia in this policy making field. Some three years ago we have created a movement in the public sector, the digital driven nation where we invited to participate in the policy making ministries which are related with the digital development of the country. We invited the companies, the ICT companies represented by the associations. We invited the society representatives when we invited the academia representatives. Together we worked on the plans where governments shall... What priorities governments shall make and we have reached significant success in this policy making approach. Recently the e-government benchmark of the European Commission has been announced and surprisingly we have found that Latvia has the fourth place in the maturity level in the e-government. We see that this approach for the policy making is very effective. We are now extending this approach making the targets, making the goals what we need, what we want to reach together with our private sector together with our society representatives and the academia. Of course it demands to change the way how we are creating the policy. The policy making shall become more advanced, more light because we need to go in the same speed with our policy development as the technologies are developing. One topic that I also wanted to... This transformation of the digital environment demands also to change the way how we are communicating between ourselves. We have communicated using the information, sharing the information, but information doesn't mean that this information is the data. We will need in the future to change the way how we are communicating between ourselves, using more data in our communication habits to support, to fit this new digital paradigm. Ending my presentation I would tell that we proudly, that we can proudly say that we actually are data-driven nation. Thank you.


and distinguished guests, Prof. Sathya Mahaptra. Thank you to all. Today's topic is Holistic Health Care. I am the Ayur System. I have been in Ayurveda for 35 years. I have been in clinical practice for more than 30 years. I have been in Ayurveda for 30 years. The Ayur system that we have been in, it has been originated in India, is Ayurveda, Siddha, what is the prevalent in South India, Unani. Unani sister-carry told that Ayurveda has a lot of Gulf countries, it has translated to Urdu and it is in Unani. We have some medicinal plants available in both countries. And then we have Himalayan Belt, जा दि आपनों को आमा भीट्गेट्टी बहुला गिला तेभे आमा चानल को लेएक, शेर, और सबस्क्रेप करीपा को जमा भी बलूं तो नहीं


Hello and welcome to the STM32L4 MOOC online training. My name is Andre Barat and I'll guide you through the RCC hands-on session. The RCC or Resetting Clock Control manages system and peripheral clocks. The STM32L4 Discovery Board has three internal oscillators, one external crystal or resonator and it also contains three-faced locked loops. Many peripherals have dual clock domain, allowing to clock them either from one of the cortex and buses or from a clock source independent of the system clock. This allows for instance the ADC to run at its full speed while the core is running on a lower speed. This will represent a saving on power consumption. The RCC also manages various resets present on this device. Using the clock configuration window of the STM32QBmx it's possible to configure all clocks inside the microcontroller with ease. As we enable the peripherals from the pinout window they will also become available here. We can see that many peripherals have several clock options. Once the microcontroller clock output feature is enabled we will also be able to select from which clock we want to output. Our goal in this example is to learn how to change a clock source on the fly using HALAPI. We will also learn how to output a selected clock from one of the low speed oscillators on a dedicated pin. This feature is also available for all the high speed clocks. Without further ado let's launch our STM32QBmx to start initializing our peripherals. When the STM32QBmx is loaded we start a new project and we will type our part number STM32L4476VG. When the part number is found we start a new project. On the pinout tab we will go to RCC and we will select LSEO clock output which is mapped on the PA2 pin. We will go to the clock configuration tab and we will realize that the LSEO source MOOCs becomes available. In our example we will be outputting the LSI oscillator. We are ready to save the project and after choosing the system workbench for STM32 as our IDE we are ready to generate the code. After the code is generated by STM32QBmx we will start by inspecting the elements of our code. We are going to check the GPIO configuration and in this case only LSEO pin is configured. Now let's have a look inside of the system clock configuration function. There are two configuration structures to be specified later on on this function. The first one is the oscillator configuration and the second is the clock source configuration. Starting with the oscillator configuration the oscillators to be configured has to be assigned to oscillator type structure members. When everything is configured the HALRCC oscillator configuration function has to be called with a pointer to the configuration structure passed as argument. The second structure is for system clock source settings and prescalers for AHB and APB bus settings. MSI will be used as clock source when we are pleased with the structure that we filled we need to call the HALRCC configuration being the first parameter the pointer to the configuration structure and the second will be the weight states for the flash. LSEO will be enabled in this function. Let's now copy the configuration structures definition to the main function. We can see all members of the structures to be used to configure the oscillators. Once again in the oscillator type must be filled the oscillators to be configured. Here we can see all the members of the clock source configuration structure. Let's start by coding and switching the system clock source on the fly. Press control space for a list of proposals. We will start by filling the oscillator type member. Let's have a look into its declaration to see what we can use. In the comments there is written that these parameters can be a value of the RCC oscillator type. Let's find these parameters by using control f. We will now configure the high speed internal oscillator as this will be our new clock source. Now we will configure its new state as we are turning it on. Let's do it in the very same way as we did in the previous case. Actually, that's the way how to work with HL peripheral drivers in general. We will select and copy RCC HSI on to its state. We will leave the calibration value as default. Now the phase locked loop configuration. This one has its own structure within the oscillator structure. There are PLL multiplication and division factors, its own clock source and state. Let's turn it on and search for possible values. Now let's choose a source for the PLL. We will be using HSI oscillator as PLL clock source. Then just multiplication and division factors remain to be configured. They will be set to run on maximum frequency which is 800 MHz. You can verify the configuration selected in the clock configuration window of the STM32QBmx. Now we can finally call the HAL RCC oscillator configuration. And the parameter to be passed is appointed to the configuration structure. If something fails and the function doesn't return HAL OK, an error handler will be called. Let's continue to the clock configuration structure. As in the previous case, the first member states which clock should be configured. Let's put them all. Using all the clock sources, we will define PLL as our main clock source. All the pre-scalers will be set to 1. This doesn't play a big role in our example as we are not using any peripheral. Now we can finally call the HAL RCC clock configuration. It expects a pointer to the configuration structure as the first argument. As a second argument, it expects a number of weight states for the flash. As we are running full speed, we will use 4 weight states. As in the previous initialization, if the code configuration function isn't executed properly, the code will jump to an error handler. Now as an optional step, we can turn off the MSI. The PLL configuration won't be changed. The remaining lines can be deleted. Let's now build our project and start our debug session. Let's insert the breakpoint on the system clock configuration function. Let's press resume and the program will execute until the breakpoint is reached. Now press step over to jump inside the function. We will check now the RCC registers. Double click to fetch registers value. In the control register, MSI is on and the rest are off. In configuration register, SW byte is set to 0 meaning that MSI is being used by the system as clock source. We will press resume again. From now on, we are in the infinite loop. So we will press pause and we will check the registers content again. The registers highlighted in red means that they have been modified. We can see now that the PLL is on and ready. The HSI is on and ready and MSI has been turned off. In the configuration register, if we reanalyze once again the SW byte, we will see that it is defined as 0x3 or in binary 1.1. This means that the PLL is being used as clock source. In the flash ACR register, latency is set to 4 weight states. The clock source has been switched. If you connect now an oscilloscope probe to PA2PIN, you will be able to monitor the LSI frequency. This will be all for this session. Thank you for watching.