Pick the right promise
A low-level course should not receive Mbed-first copy, while an IoT course should not be forced into register-level language.
STM32 campaign paths
Choose the STM32 path that matches your course.
Low-level microcontroller courses and Mbed/IoT courses need different messages. Start from the path that fits the professor's actual teaching model.
Audience
University embedded systems, microcontroller, IoT, mechatronics, and hardware/software courses
Use this chooser for older shared links and secondary context pages. For an email campaign, link directly to the relevant demo first, then use the matching campaign page or return page as the bridge into a small course trial.
Register-level C, assembly, and no-library microcontroller courses
Embedded software and IoT courses using Mbed or higher-level workflows
Upload-only access where students compile locally and run on remote hardware
Board/peripheral discussions where the exact course requirements matter
STM32 C / bare-metal / upload
For register-level C, assembly, no-library, upload-only, and low-level microcontroller courses where Mbed-first messaging would be wrong.
STM32 Mbed / IoT workflow
For embedded software, rapid prototyping, IoT, and higher-level workflows where the Mbed demo is a useful first proof.
Demo path
Keep the first interaction concrete.
Keep the demo direct
Campaign emails should still send the primary click to a tracked instant demo, then use the return bridge for course-trial conversion.
Use a page as context
The campaign page handles objections, links to canonical lab resources, and keeps the trial conversation focused.
Two professor messages
Separate pages avoid presenting Mbed as the default answer for every STM32 instructor.
Direct demo first
The page supports the funnel without adding friction before the real-hardware moment.
Better trial scoping
Each path makes board, peripheral, language, and access-model requirements clearer before sales follow-up.
Positioning note
If you are unsure which STM32 route to use
Use the low-level path when the course outcome is register-level control, assembly, toolchain work, or upload-only board access. Use the Mbed path when the value is embedded software, IoT, fast prototyping, and a visible hardware interaction.
Related labs
Continue from existing LabsLand laboratories.
These public lab pages come from the current catalog, so they remain useful as SEO pages and as a route into institution access.
LabsLand ARM Community
STM32 Nucleo (C)
Programar um verdadeiro microcontrolador ARM com diferentes periféricos e modos de baixa potência.
Ver laboratórioLabsLand
STM32 Nucleo (Mbed)
Programar um microcontrolador ARM real com periféricos e modos de baixa potência usando um IDE Mbed online.
Ver laboratório
LabsLand ARM Community
STM32 Nucleo (No IDE)
Programar um verdadeiro microcontrolador ARM com diferentes periféricos e modos de baixa potência.
Ver laboratórioSTM32 C / bare-metal route
Use this route when the course needs low-level C, assembly, direct upload, or no-library workflows.
STM32 Mbed route
Use this route for embedded software, IoT, and higher-level Mbed workflows.