Uživatelská příručka pro SILICOM AN1508 Power Manager

The Power Manager is a comprehensive solution designed to optimize power usage in SiWG917, helping user achieve better energy efficiency and increased battery life. It incorporates Free RTOS tickless idle mode, which minimizes power usage by transitioning the SiWG917 M4 into a low-power state when Free RTOS operates on the Idle task.

Tento dokument poskytuje overview z klíčových funkcí Power Manageru s režimem nečinnosti bez tikání. Dále se zabývá důležitými aspekty práce s Power Managerem.

The users using Power Manager must have comprehensive knowledge of SiWG917 M4
power states. The information about the SiWG917 low-power modes and current consumption in different power modes and power states is in AN1430: SiWG917 Low-Power Application Note.

KLÍČOVÉ BODY

• Introduction to Power Manager in SiWG917
• Power Manager Architecture, features and advantages
• Power State Transition with Power Manager APIs
• Considerations while using Power Manager

Architektura správce napájení

Správce napájení je služba na úrovni platformy, která spravuje stavy napájení M4 a jejich přechody na vyžádání aplikace. Tyto požadavky jsou nastaveny různými softwarovými moduly (ovladači, zásobníky, kód aplikace atd.).

Obrázek 1.1. Architektura Power Manageru

• Application tasks represent tasks running in the application. Users call the Power Manager service APIs from the application tasks.
• Power Manager Service Layer interacts with the application layer tasks. It is a layer over the existing internal core API layer simplifies the process for users to develop their applications.
• Middle Layer is a supporting layer for Power Manager service. It validates the power state transitions.
• Internal API Layer is the low-level driver which interacts with hardware layer where the register level configurations are done.

Features of Power Manager

• It is an Interface between software modules and the device, offering APIs to efficiently manage and configure the power state transitions of SiWG917.
• The SiWG917 M4 entry into a power state is determined by the requirements. Using the requirement APIs, requirements for a specific power state can be added or removed.
• It offers a notification mechanism, providing an option for subscribing/unsubscribing to events during state transitions, i.e., while entering or leaving any state. Based on the subscription, the Power Manager provides notifications through a callback function to the application. The notification events include Power State
• Transition, exit from sleep, and exit from standby mode. The main purpose of these notifications is for different software modules to adapt to the new power state.
• The Power Manager checks if it is ok to sleep and then enters the sleep..
• The clock scaling feature in differentiating system clock configuration in PS4 and PS3 active state is done. It can be switched be-tween performance and power-save. By-default it is configured as power-save at the time of state change.
  Poznámka: PS1 check release notes on the current support for PS1 with Power Manager.

AdvantagSprávce napájení

• Integrating Power Manager into an application is seamless and provides following configurations. The
• configurations made in the UC in Simplicity Studio will be saved, allowing the Power Manager APIs to be reused as needed.
• Handles peripherals, RAM banks and wake-up source configuration. Required peripherals can be enabled/disabled to reduce power consumption.
• Enabling RAM retention, peripherals to be powered on, setting the wake-up sources.
• Provides easy and convenient ways to control all the power modes i.e., Active, Standby and Sleep as well as supporting all the pow-er state transition i.e., PS4, PS3, PS2, PS1, PS0.
• To prevent race conditions and ensure secure concurrent access, the Power Manager APIs include safeguards such as enabling and disabling interrupts.
• Power Manager uses sleep timer for precision timing.

Poznámka:

• The state hierarchy ranges from PS4 to PS0, with PS4 being the highest power state. However, the sleep mode in any power state is considered the lowest state. The Power Manager, with tickless mode, enables the system to enter sleep mode when the scheduler has no tasks to process.
• To know more about the Power states, please visit AN1430: SIWG917 Low-Power Application Note.

Komponenty

Power Manager Components facilitate the user to configure the RAM retained, the peripherals to remain powered on/off, and sets the wake-up sources prior to the M4 entering sleep mode. Following are the Power Manager components (enabled using the UC in Simplic-ity Studio):

• Správce napájení
  • Power Manager Configuration
  • Wakeup source Configuration
    • Calendar Wakeup
    • GPIO Wakeup
    • Deep Sleep Timer
    • Wireless Wakeup
• UULP peripheral component for the selected wake-up source
• Nízký výkon

Chcete-li se dozvědět více o instalaci komponent pro integraci Power Manageru, navštivte stránku Integrace Power Manageru.

Součást Správce napájení
Služba Power Manager se inicializuje s instalací této komponenty, uživatel službu Power Manager inicializovat nemusí.

Obrázek 2.1. Součást Power Manageru

Následující komponenty se automaticky nainstalují při instalaci komponenty Power Manager.

Komponenta SI91X BEZ TICK-LESS
The Tickless idle mode feature will suspend the SiWG917 M4 and keep it in sleep when no tasks are scheduled to run.

Součást konfigurace Power Manageru
There are two components pertaining to the Power Manager configuration,

• Power Manager Advance Configuration
• Power Manager Configuration

These components provide control over peripheral enable/disable and RAM retention. Peripheral and RAM retention is configured with
the installation of this component, user intervention is not required.
Poznámka: The user can install either ‘Power Manager Configuration’ or ‘Power manager Advance Configuration’ component.

Obrázek 2.2. Součást konfigurace Power Manageru

Power Manager Configuration
This component is a basic configuration component in which the user can select which peripherals need to be powered on/off according
to the domain of the peripheral.

Konfigurace periferií

• High Power Peripherals (available in PS4/PS3 power states)
• Low Power Peripherals (available in PS2 power states)
• Ultra Low Power Peripherals (available in all power states)

The peripheral availability in different power states and the list of different group of peripherals for which power is controlled through software is given in ‘M4 Power States’ section of AN1430: SiWG917 Low-Power Application Note.

Figure 2.3. Power Manager Configuration – Peripheral Configuration

Konfigurace RAM
This component also provides configuration for RAM retention. Two options are provided to configure the RAM banks i.e. using size or bank number. The user needs to select any one option.

Figure 2.4. Power Manager Configuration – RAM Configuration

Poznámka: If both RAM banks using size & bank numbers are enabled, RAM banks using size will be configured by default.

Power Manager Advance Configuration
This component is an advance configuration component in which the unwanted peripherals and RAM banks are powered off as shown
in the following figure by default. Configurations in this are made to get the optimum power consumption.

Konfigurace periferií

• High Power Peripherals (available in PS4/PS3 power states)
• Low Power Peripherals (available in PS2 power states)
• Ultra Low Power Peripherals (available in all power states)

Poznámka: SiWG917 M4 current may vary as per the selection of peripherals in addition to the default configuration.

Figure 2.5. Power Manager Advance Configuration – Peripheral Configuration

Konfigurace RAM
The default configuration for RAM retention is already configured to provide the lowest SiWG917 M4 current but if required, the user can configure the RAM banks using size or bank number.
Poznámka: SiWG917 M4 current may vary as per the selection of RAM banks in addition to the default configuration.

Figure 2.6. Power Manager Advance Configuration – RAM Configuration

Komponenta konfigurace zdroje probuzení
This component provides the initialization and configuration for the UULP wake-up sources used in PS4 sleep/PS3 sleep/PS2 sleep.

The UULP wakeup sources that are provided are as follows,

• Calendar or Alarm Wakeup
• GPIO Wakeup
• Deep Sleep Timer Wakeup
• Wireless Wakeup
  
  Obrázek 2.7. Součást konfigurace zdroje probuzení v nástroji Power Manager

Poznámka: The user must install the respective UULP peripheral components that are selected as a wake-up source. This would get all the dependencies and filesouvisející s vybraným periferním zařízením.

Calendar or Alarm Wakeup
Zdroj probuzení kalendářem nebo budíkem lze povolit a konfigurovat v sekundách a milisekundách. Ve výchozím nastavení je zdroj probuzení budíkem nakonfigurován s 5sekundovou spouštěcí lhůtou. Tento zdroj probuzení lze povolit pomocí přepínače.

The alarm timer starts running as soon as the wakeup source is initialized prior to M4 sleep and triggers an interrupt upon the timer expiry. The M4 wakes up upon this interrupt.

Poznámka: Milli second timer is recommended to be used, when M4 is in active state. Because the sleep and wake-up transition of M4 takes ~8 ms. The suggested minimum value for this timer is 100 ms.

Alarm time reconfiguration during runtime is not possible with Power Manager. If a user wants to change alarm time in runtime, the user should configure the alarm wake-up source manually with ‘sl_si91x_power_manager_set_wakeup_sources()’ API without using UC. So, in this case, the initialization of the wake-up source should be done by the user in the application.
Poznámka: The alarm timer is periodic as it is configured every time M4 enters sleep inside the ‘sl_si91x_power_manager_sleep()’.

Obrázek 2.8. Probuzení podle kalendáře

GPIO Wakeup
There are 4 UULP GPIO (0 to 3) available as mentioned following figure which can act as a wake-up source. Enabling the GPIO Wakeup allows the user to select the desired GPIO pin as a wake-up source.

The SiWG917 M4 wakes up based on the input from the configured UULP GPIO. Users can configure the polarity of the GPIO wakeup
zdroj.

Obrázek 2.9. Probuzení GPIO

Deep Sleep Timer
Deep Sleep Timer is used as wakeup source for the SiWG917 M4 in sleep. This timer works only during M4 sleep. The sleep time is configurable in micro-seconds.

Poznámka: Even if the user configured the timer when M4 is in active state, this timer will start when M4 enters sleep mode. The maximum configurable time is 232 micro-seconds (~71 minutes).

Obrázek 2.10. Probuzení časovačem hlubokého spánku

Wireless Wakeup
This wake-up source is used when the user wants to wake up M4, when a wireless remote message is received by the NWP. Upon receiving the message, NWP will trigger the M4 to wake up.

Figure 2.11. Wireless Wakeup

Nízkoenergetická periferní součástka
Low Power Peripheral component is for using the ULP peripheral in PS2 state. The installation of this component will move the required driver files to RAM as in PS2 state, the flash will be turned off and M4 can execute from RAM.

Poznámka: Initialization and configuration of the peripheral should be done by the user manually in the application.

For more information, please refer to Power Manager Components integration.

Rozhraní API pro správu napájení
Tato část popisuje některá rozhraní API nabízená produktem Power Manager. Další informace o rozhraních API a jejich příkladech…ampsoubory naleznete v dokumentaci k rozhraním API správce napájení.

Tabulka 3.1. Rozhraní API pro Power Manager

API	Popis
sl_si91x_power_manager_init	Inicializace služby Power Manager.
sl_si91x_power_manager_add_ps_requirement	Přidat požadavek na stavy napájení.
sl_si91x_power_manager_remove_ps_requirement	Odstranit požadavek na stavy napájení.
sl_si91x_power_manager_set_clock_scaling	To configure the clock scaling  Power save and Performance.
sl_si91x_power_manager_add_peripheral_requirement	Přidává požadavek na periferní zařízení.
sl_si91x_power_manager_remove_peripheral_requirement	Aby se odstranil požadavek na periferní zařízení.
sl_si91x_power_manager_subscribe_ps_transition_event	Registrace zpětného volání, které bude voláno při daném přechodu (přechodech) stavu napájení.
sl_si91x_power_manager_unsubscribe_ps_transition_event	Zrušení registrace popisovače zpětného volání události při změně stavu napájení.
sl_si91x_power_manager_sleep	To move into sleep mode and wait for the peripheral to be set as a wakeup source to trigger and wake up the M4.Poznámka: Applications using RTOS with tickless mode enabled must not call this function. This API is not supposed to be used directly in the application and is called automatically when system is in idle state with tickless mode.
sl_si91x_power_manager_set_wakeup_sources	To configure the wakeup sources.
sl_si91x_power_manager_configure_ram_retention	To retain the RAM in low power state either by using size or RAM bank as input parameters.
sl_si91x_power_manager_get_current_state	To return the current power state.
sl_si91x_power_manager_get_requirement_table	To get the current requirements on all the power states.
sl_si91x_power_manager_deinit	To de-initialize the Power Manager service.

Správce napájení s funkcí nečinnosti bez tikání
Power Manager Tickless Mode is a feature provided by the Free RTOS that allows the SiWG917 to reduce power consumption by entering a low-power mode when there are no tasks to execute.

V tradičních implementacích RTOS se používá periodické přerušení časovače, známé jako tick, ke sledování času a spouštění plánovače RTOS, který určí, která úloha by se měla spustit jako další. V aplikacích, kde je spotřeba energie kritická, však může být neustálé generování přerušení časovače neefektivní a vést ke zbytečné spotřebě energie.

Tickless mode in Free RTOS addresses this issue by dynamically adjusting the timing of the tick interrupt based on the requirements of the tasks. When there are no tasks ready to execute, the SiWG917 M4 can enter sleep mode, effectively reducing the frequency of timer interrupts and conserving power.

Poznámka: As Tickless Idle mode configures Sys RTC as a mechanism to generate the Real-Time Operating System (RTOS) ticks. These ticks are essential for the RTOS to manage timing and scheduling tasks effectively. It is strongly advised against utilizing the Sys RTC peripheral for any purpose other than its designated functionality.

Implementace
A low-power idle hook function that Free RTOS will call when there are no tasks ready to execute is implemented. This hook function
should put the SiWG917 M4 into sleep.

Figure 4.1. Tickless Idle Mode Implementation in Free RTOS

1. The application tasks call os Delay, v Task Delay, os Semaphore Acquire or other blocking functions, leading the scheduler to consider them idle. When there are no tasks to be executed, the application will execute Free RTOS idle hook.
2. The application checks if the expected idle time is greater than or equal to a predefined threshold (config EXPECTED IDLE TIME BEFORE SLEEP), which is set to 100 milliseconds. If the condition is met, the application suspends all tasks.
3. The application then calls a function specifically designed to handle the M4 transition to low power mode port SUP-PRESS_TICKS_AND_SLEEP(x Expected idle Time) and IRQs are disabled to ensure that no interrupts occur while the system is preparing to enter low power mode..
4. Then the application checks for the following before letting M4 go to sleep.
   • Check Active Events: It checks if any ongoing tasks or operations require the system to remain active, for example, data trans-mission, sensor readings, or critical computation. Also checks if there is any requirement added, and the device goes to sleep if there is no power manager requirement added.
   • System Flags: Internal flags or states that indicate whether it is appropriate to sleep or not are likely checked. Checking the pending packets from NWP while M4 going to sleep.
   • Flash operation: Check if there are any flash write operations like NVM command is in progress and the device goes to sleep if there are no flash operations.
5. If the M4 processor is ready to go to sleep mode, it calls the M4 sleep API (sl_si91x_power_manager_sleep()) to put the M4 pro-cessor into sleep mode.
6. The M4 processor wakes up from sleep mode when a predefined wakeup source triggers it. Once it wakes up, the duration for which the system was in sleep mode (known as sleep ticks) is added to the RTOS.
7. IRQs are enabled after the system wakes up from sleep mode and all tasks that were suspended are resumed, and the application continues normal operation.

Poznámka:

• The user must be cautious when using os Semaphore Acquire and os Delay, as the M4 enters sleep during this configured delay time and will not serve any event interrupts.
• Power Manager component shall install the wireless wake-up and Sys RTC component for sleeptimer as wake-up resource by de-fault. It is highly recommended not to install these components explicitly.

Pokud nejsou žádné úlohy připraveny ke spuštění, jádro přejde do nečinného režimu bez tikání. Systém se probudí po vypršení časovače spánku nebo po jakémkoli nakonfigurovaném zdroji probuzení. Zde je základní vývojový diagram ilustrující chování systému.

Figure 4.2. Interaction between the Task, Power Manager, and Free RTOS kernel

Případy použití

Application with Peripheral only
Režim nečinnosti bez tikání automaticky aktivuje funkci spánku, když plánovač přejde do nečinnosti. Power Manager má API, která zabraňují systému v přechodu do režimu spánku.

When a requirement is added for a power state, then the system is prevented from entering sleep as there is a requirement higher than sleep mode is added. Make sure to remove the higher requirement added if the user wants to let the M4 enter sleep mode in tickless idle mode. For instance, during data transmission on a USART, the system can enter sleep mode if there is any delay during transmission. To address this, the Power Manager adds a requirement on PS4 before initiating the transfer and removes the requirement once
the transfer is complete, thereby preventing the M4 from entering sleep mode.
Below is the flow for how to handle peripherals across sleep wakeups with tickless idle

Figure 4.3. Handling Peripherals with Tickles Idle Mode

Application with Wireless Functionalities and Peripherals
A sequence flow illustrating a use case for wireless applications that utilize peripherals with tickles idle mode.

1. Power state (PS4) requirement is added to prevent the M4 entering sleep during any delay unintended.
2. The SiWG917 initializes the NWP and M4 peripheral.
3. The NWP is configured as a WLAN station, connects to an Access Point (AP) and establishes a connection to the Cloud.
4. The NWP is set to Connected Power Save mode (Associated Power Save).
5. The peripheral activity is carried out and data is collected. The peripheral is un-initialized before entering M4 sleep.
6. The power state requirement is removed allowing the M4 to enter sleep.
7. The M4 is waiting on a semaphore with defined wait time. The RTC timer, UULP GPIO, and Wireless message are defined as wakeup sources.
8. The M4 enters last active state (PS4) sleep mode with retention as the scheduler is idle.
9. Upon a GPIO interrupt/ RTC timer expiry/ wireless message/ semaphore wait time expiry, the M4 wakes up.
10. Upon M4 wakeup, add the power state requirement (PS4).
11. For performing the peripheral activity again, re-initialize the peripheral and execution continues from step 5.
    
    Obrázek 4.4. Obsluha periferií s bezdrátovou aktivitou v klidovém režimu Tickles

Sekvenční diagram
On boot up the power manager starts with PS3 power save state (40MHz) and after that application adds its required state through API calls.
Sekvenční diagram pro přechod ze stavu PS3 do PS2 je následující.

Obrázek 5.1. Sekvenční diagram znázorňující přechod ze stavu PS4 do stavu PS2

The Power Manager service is initialized by default using the sl_si91x_power_manager_init() function, which sets the processor to the PS3 state with a clock speed of 40 MHz (Power Save). All possible events are subscribed to using the sl_si91x_power_manag-er_subscribe_ps_transition_event() function, which includes the callback function address.

To add a requirement for the PS2 state, the sl_si91x_power_manager_add_ps_requirement() function is used. The sli_si91x_pow-er_manager_update_ps_requirement() function then updates the power state requirement, current state, and requirement table, en-suring that the added requirement is a valid transition.

Funkce sl_si91x_get_lowest_ps() ověřuje všechny požadavky na stav napájení a vrací možný přechod stavu na základě hierarchie stavů. Napříkladample, if both PS4 and PS2 state requirements are added, the function will return PS4 as the possible transition since it is considered higher than PS2. The system will not transition to PS2 until the PS4 requirement is removed. However, here as only the PS2 state requirement is added, the function will returm PS2 as the possible transition.

Nakonec funkce sli_si91x_power_manager_change_power_state() aktualizuje stav napájení z PS3 na PS2 a funkce ps3_to_ps2_state_change() provede tento přechod pomocí interních API.

Přechody stavu napájení
This section provides a simple illustration for power state transition using Power Manager APIs.

• To add a power state requirement-si_si9ix_power_manager_add_ps_requirement (sl_power_state_t state
• To remove a power state requiremental si9lx_power_manager_remove_ps_requirement (sl_power state_t state);
• The power states are
  • SL SI91X_POWER MANAGER_PSO PSO Power State
  • SL SI91X POWER MANAGER PS2 PS2 Power State
  • SL_SI91X_POWER_MANAGER_PS3 -PS3 Power State
  • SL SL_SI91X_POWER_MA SI91X POWER MANAGER PS4 PS4 Power State

Poznámka:

• Requirement table stores the requirements for each power state and based on that power manager decides the current state. sl_si91x_power_manager_get_requirement_table API is used to get the current requirements on all the power states.
• If a task wants to enter a low power mode (such as PS3 or PS2), it first checks if any other task has a higher requirement.
• When multiple tasks request a state transition, the Power Manager maintains the possible state transitions. It is recommended that a task checks the requirement table before switching and performs the state change accordingly.
  
  Obrázek 5.2. Přechody mezi stavy napájení

Úvahy
Tato část se zaměřuje na aspekty, které je třeba vzít v úvahu při práci s programem Power Manager.

Add/Remove PS requirement
Aktuální stav M4 je poslední aktivní stav, do kterého přešla. Například pokud je požadavek na stav PS4 přidán a poté odebrán, následuje přidání a odebrání stavu PS3, aktuální stav M4 by byl PS3.

In a multi-threaded application,

• There may be many requirements added, and Power Manager is maintaining the highest state requested.
• All the requirements of the higher power state must be removed for the M4 to transition to the next lower power state.
• If multiple requirements are added, the state will change upon removing all the requirements.

Remove peripheral requirement
Pokud je jakékoli periferní zařízení ve stavu PS4 deaktivováno (napříkladample, disabling SSI), upon switching to the PS2 state and then back to the PS4 state, all peripherals will be powered on during the state transition. The sl_si91x_power_manager_remove_peripheral_require-ment() can be used again to disable the required peripherals.

Measuring power consumption
To measure the power consumption of only,

• NWP – Configure M4 in PS0 without any RAM retention.
• M4 Configure NWP in DEEP_SLEEP_WITHOUT_RAM_RETENTION (Deep Sleep without RAM retention when the device is not associated with AP).

Dodatek

Tabulka 7.1. Tabulka zkratek

SN	Zkratka	Popis
1	AP	Přístupový bod
2	API	Aplikační programovací rozhraní
3	GPIO	General Purpose Input/ Output
4	NWP	Síťový procesor
5	PS	Power States (PS4, PS3, PS2, PS1, PS0)
6	QSPI	Quad sériové periferní rozhraní
7	BERAN	Paměť s náhodným přístupem
8	RTC	Hodiny reálného času
9	RTOS	Operační systém v reálném čase
10	SSI	Synchronní sériové rozhraní
11	UC	Universal Configurator
12	ULP	Ultra nízká spotřeba
13	UULP	Ultra Ultra Low Power
14	USART	Univerzální synchronní/asynchronní přijímač/vysílač
15	WLAN	Bezdrátová místní síť

Historie revizí

Revize 1.0
června 2025
Počáteční vydání.

Studio jednoduchosti
Přístup jedním kliknutím k MCU a bezdrátovým nástrojům, dokumentaci, softwaru, knihovnám zdrojového kódu a dalším. K dispozici pro Windows, Mac a Linux!

Portfolio IoT
www.silabs.com/IoT

SW/HW
www.silabs.com/simplicity

Kvalitní
www.silabs.com/quality

Podpora a komunita
www.silabs.com/community

Zřeknutí se odpovědnosti
Silicon Labs má v úmyslu poskytovat zákazníkům nejnovější, přesnou a hloubkovou dokumentaci všech periferií a modulů dostupných pro implementátory systémů a softwaru, kteří používají nebo hodlají používat produkty Silicon Labs. Charakterizační údaje, dostupné moduly a periferie, velikosti paměti a adresy paměti se vztahují ke každému konkrétnímu zařízení a poskytnuté „typické“ parametry se mohou v různých aplikacích lišit a mění se. Aplikace exampzde popsané texty slouží pouze pro ilustrativní účely. Společnost Silicon Labs si vyhrazuje právo provádět změny bez dalšího upozornění v informacích o produktech, specifikacích a popisech zde uvedených a neposkytuje žádné záruky na přesnost nebo úplnost obsažených informací. Bez předchozího upozornění může společnost Silicon Labs aktualizovat firmware produktu během výrobního procesu z důvodu bezpečnosti nebo spolehlivosti. Tyto změny nezmění specifikace ani výkon produktu. Silicon Labs nenese žádnou odpovědnost za důsledky použití informací uvedených v tomto dokumentu. Tento dokument neimplikuje ani výslovně neuděluje žádnou licenci k navrhování nebo výrobě jakýchkoli integrovaných obvodů. Produkty nejsou navrženy ani schváleny k použití v zařízeních třídy III FDA, aplikacích, pro které je vyžadováno schválení FDA před uvedením na trh, nebo v systémech podpory života bez konkrétního písemného souhlasu Silicon Labs. „Systém podpory života“ je jakýkoli produkt nebo systém určený k podpoře nebo udržení života a/nebo zdraví, u kterého lze důvodně předpokládat, že pokud selže, povede k vážnému zranění nebo smrti. Produkty Silicon Labs nejsou navrženy ani schváleny pro vojenské aplikace. Produkty Silicon Labs se za žádných okolností nesmějí používat ve zbraních hromadného ničení, včetně (ale nejen) jaderných, biologických nebo chemických zbraní nebo střel schopných takové zbraně nést. Silicon Labs se zříká všech výslovných a předpokládaných záruk a nenese odpovědnost za jakákoli zranění nebo škody související s používáním produktu Silicon Labs v takových neautorizovaných aplikacích.

Informace o ochranné známce
Silicon Laboratories Inc., Silicon Laboratories, Silicon Labs, SiLabs and the Silicon Labs logo, Blueridge, Blueridge Logo, EFM, EFM32, EFR, Ember, Energy Micro, Energy Micro logo and combinations thereof, “the world’s most energy friendly microcontrollers”, Repine Signals, WiSe Connect, n-Link, EZ Link, EZ Radio, EZRadioPRO®, Gecko, Gecko OS, Gecko OS Studio, Precision32, Simplicity Studio, Telegesis, the Telegesis Logo, USBX press, Zentri, the Zentri logo and Zentri DMS, Z-Wave”, and others are trademarks or registered trademarks of Silicon Labs. ARM, CORTEX, Cortex-M3 and THUMB are trademarks or registered trademarks of ARM Holdings. Keil is a registered trademark of ARM Limited. Wi-Fi is a registered trademark of the Wi-Fi Alliance. All other products or brand names mentioned herein are trademarks of their respective holders.

Silicon Laboratories Inc.
400 West Cesar Chavez
Austin, TX 78701
USA
www.silabs.com

Dokumenty / zdroje

Správce napájení SILICOM AN1508 [pdfUživatelská příručka AN1508, SiWX917, AN1508 Správce napájení, Správce napájení

Reference

• Uživatelská příručka