Skip to content

Course Q&A

4 Topics 4 Posts

Questions about Embiq course blocks. One sub-category per block.

This category can be followed from the open social web via the handle course-q-a@forum.grapesiot.com

Subcategories


  • Questions about Electronics, MCU Architecture, Embedded C, GrapesIDE setup

    1 1
    1 Topics
    1 Posts
    A
    Block 1 — Foundation Resources All session content lives at docs.embiq.in/block1/ Session Topic Docs Link 1.1.1 Voltage, Current & Power → docs 1.1.2 Reading Datasheets → docs 1.1.3 Multimeter & Oscilloscope → docs 1.1.4 Component Identification → docs 1.2.1 MCU vs CPU vs MPU → docs 1.2.2 Memory Map → docs 1.2.3 GPIO Deep Dive → docs 1.2.4 Clock System + First Flash → docs 1.3.1 Bit Manipulation → docs 1.3.2 Pointers in Embedded C → docs 1.3.3 volatile / const / static → docs 1.3.4 Structs & HAL → docs 1.4.1 GrapesIDE Workflow → docs 1.4.2 Serial Logging → docs 1.4.3 Compiler Errors → docs 1.4.4 Git & Version Control → docs Post questions in this category. Tag with the session number e.g. 1.1.2
  • Questions about UART/SPI/I2C/ADC, Interrupts, FreeRTOS, Firmware Architecture

    1 1
    1 Topics
    1 Posts
    A
    Block 2 — Embedded Core Resources All session content at docs.embiq.in/block2/ Session Topic 2.1.1 UART Deep Dive 2.1.2 SPI — Master/Slave, Timing 2.1.3 I2C — Addressing, Clock Stretch 2.1.4 ADC — Sampling, Noise 2.2.1 Interrupts & NVIC 2.2.2 GPIO Debounce 2.2.3 Timer & PWM 2.2.4 Interrupt Bugs 2.3.1 Why RTOS 2.3.2 FreeRTOS Tasks 2.3.3 Queues 2.3.4 Semaphores & Mutexes 2.3.5 Memory Management 2.3.6 RTOS Bugs 2.4.1 State Machines 2.4.2 HAL Design 2.4.3 Error Handling & Watchdog 2.4.4 Event-Driven Architecture
  • Questions about MQTT, TLS, Security, Modbus RTU, BLE provisioning

    2 2
    2 Topics
    2 Posts
    A
    A connected device without security is a loaded gun pointed at your own network — and MQTT isn't the answer to every device-side problem either. This companion post covers the two things that turn a working prototype into shippable firmware: locking it down, and reaching beyond MQTT where it fits. Lock it down Mutual TLS, done right. Server-only TLS leaves devices talking to impostors. Both sides prove identity — the device verifies the server, the server verifies the device. Two field gotchas: actually validate the CA chain (skipping verification "temporarily" becomes permanent), and sync the clock first — certificates look invalid on a device that thinks it's 1970. → Why security matters — real attacks → Certificate-based auth and device tokens Trust the code you run. Secure boot stops modified firmware from executing; signed OTA with hash verification plus automatic rollback stops a bad or malicious update from bricking the fleet. Credentials live in protected on-device storage with a provisioning flow — never as string literals in source. Assume anyone can dump your flash; design so a dump alone isn't enough. → The secure boot concept → Credential storage on the device → Secure OTA with signed firmware Reach beyond MQTT HTTP/REST for on-device APIs and cloud calls, WebSocket for local dashboards, Modbus RTU for industrial sensors on RS-485 that isn't going away, and BLE provisioning so users can configure WiFi credentials without hardcoding them. → HTTP and REST from the device → WebSocket basics for local dashboards → Modbus RTU for industrial devices → BLE provisioning of WiFi credentials Capstone A fully connected, secure IoT device — TLS-authenticated MQTT link to GrapesIoT, a clean topic schema, LWT-based presence detection, and offline buffering that survives a broker outage. Share your build in the lab submissions area when it's done. Post questions here and tag with security, tls or ble. For the device-to-cloud path (networking, MQTT, patterns), see the companion post above.
  • Questions about GrapesIoT, TimescaleDB, Fleet management, OTA, Analytics

    0 0
    0 Topics
    0 Posts
    No new posts.
  • Questions about the 48h torture test, hardening checklist, industry defense

    0 0
    0 Topics
    0 Posts
    No new posts.