sandeepmistry/arduino-nRF5

inttypes are not handled correctly (PRIu8)

Open

#197 opened on Oct 1, 2017

View on GitHub
 (6 comments) (0 reactions) (0 assignees)C (288 forks)github user discovery
help wanted

Repository metrics

Stars
 (952 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

This sketch demonstrates printing to a string using defines of inttypes.h. The PRIu8 isn't interpreted correctly.

void setup() {
  Serial.begin(115200);
}

void loop() {
  char fmtBuffer[400];
  snprintf(fmtBuffer, sizeof(fmtBuffer), "hu=%hu PRIu8=%" PRIu8 " PRIu16=%" PRIu16 " PRIu32=%" PRIu32, 1, 1, 1, 1);
  Serial.println(fmtBuffer);
}

Output is: hu=1 PRIu8=hu PRIu16=1 PRIu32=1

Contributor guide

Research direction
Check the definition of PRIu8 in inttypes.h for the nRF5 toolchain and trace how the printf like function interprets format specifiers.
Tech stack
c
Domain
embedded iot
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C programming basicsArduino
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70