Corebit s.r.o.

Firmware that holds up on real hardware.

We develop and debug embedded software for product teams — from first board bring-up to firmware you can ship and maintain.

CH1 IRQ · CH2 SCL · CH3 SDA● Trigger: IRQ falling400 kHz · 1 µs/div
Logic analyzer capture: a sensor interrupt triggers an I2C write of 0x0F to address 0x48 IRQSCLSDAI²C S0x48 · writeA0x0FAP Δt 4.8 µs
  • Company, not a middlemanContract directly with the engineers doing the work.
  • EU-basedSlovakia, CET timezone, invoicing in EUR.
  • Your code, your IPFull source and rights transferred on payment.
  • Reply within 1 business dayTo every project enquiry.

What we build and fix

Focused support for teams that need to ship a device, solve a stubborn problem, or add experienced hands without a long hiring cycle.

Firmware development

Readable, maintainable C and C++ for new products, new features and existing codebases — bare-metal or on an RTOS.

  • C / C++
  • FreeRTOS
  • Zephyr
  • Bare-metal

Drivers and peripherals

Low-level drivers that make sensors, radios and actuators behave — with timing and error handling you can rely on.

  • SPI
  • I²C
  • UART
  • CAN
  • BLE

Board bring-up and debugging

We trace faults across hardware and software with a scope, a logic analyzer and a debugger, and hand back findings you can act on.

  • JTAG / SWD
  • Logic analysis
  • Root cause

Connected devices

Firmware that talks reliably to gateways and the cloud — including secure over-the-air updates and device provisioning.

  • MQTT
  • OTA updates
  • Provisioning

Toolbox

Technology follows the product's requirements — power budget, unit cost, interfaces and who maintains it next — not the other way round.

LanguagesEmbedded C, C++, Python for tooling and tests
PlatformsARM Cortex-M (STM32, nRF52/nRF53), ESP32
RuntimeBare-metal, FreeRTOS, Zephyr
InterfacesUART, SPI, I²C, CAN, BLE, Wi-Fi
VerificationUnit tests on host, hardware-in-the-loop, static analysis
DeliveryGit, CI builds, code review, written handover

Edit this table to list only what you actively support.

How a project runs

Short feedback loops and something concrete at every stage — so you always know where the project stands.

  1. Understand

    Product context, constraints, interfaces, risks and a shared definition of done.

    You get: a written scope and estimate
  2. De-risk

    The riskiest assumption is tested first with a small experiment on real hardware.

    You get: a go / no-go finding
  3. Build and verify

    Work lands in visible increments, tested on target and reviewed with your team.

    You get: regular builds and demos
  4. Hand over

    Source, build instructions, tests and the documentation the next engineer needs.

    You get: a project you fully own

Ways to work together

Pick the model that fits how clear your scope is today. We can switch as the project matures.

Technical assessment

When something isn't working and you need to know why.

A fixed-price, short engagement: code or board review, fault analysis, a written report with recommendations.

  • Fixed price, agreed upfront
  • Typically 3–10 days

Ongoing engineering

When you need capacity on an evolving product.

Dedicated engineering time each month, working inside your tools, repo and sprint process.

  • Monthly hours, rolling contract
  • Weekly progress summary

Typical problems we solve

Representative scenarios. Replace them with real, client-approved case studies as soon as you have them.

Prototype → baseline

New sensor board bring-up

First boards are back, nothing talks yet, and the app team is waiting.

Approach
Validate every interface, write drivers, add a debug console.
Outcome
A firmware baseline the team can extend.
Field fault → fix

Intermittent lock-ups in the field

Devices freeze every few days and nobody can reproduce it on the bench.

Approach
Fault logging, stress tests, trace capture, root cause.
Outcome
A verified fix and diagnostics that stay in the product.
Device → cloud

Connecting an existing product

A working device needs telemetry and remote updates without a redesign.

Approach
Communication stack, secure OTA updates.
Outcome
A fleet you can monitor and update remotely.

Common questions

Can you work under an NDA?

Yes. We're happy to sign your NDA before you share any details, or send ours.

Who owns the code?

You do. Full source code and intellectual property rights transfer to you on payment, as stated in the contract.

Do you work with clients outside Slovakia?

Yes. We work remotely with teams across the EU and beyond, in English. Hardware is shipped to us for testing on target.

Do you also design the hardware?

Our focus is software. We review schematics from the firmware point of view and work closely with your hardware designer or a partner.

How quickly can you start?

Assessments can usually start within one to two weeks. Larger projects depend on current capacity — we'll give you a concrete date in the first reply.

Enter your name.
Enter a valid email address, e.g. name@company.com.
What do you need? (pick any)
Add a short description so we can prepare a useful reply.
Please confirm consent so we can reply.