Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
E
e7020e_2019
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Anton
e7020e_2019
Commits
4a3c6cae
Commit
4a3c6cae
authored
6 years ago
by
anttib-5
Browse files
Options
Downloads
Patches
Plain Diff
bare10_1
parent
9fe310d5
No related branches found
No related tags found
No related merge requests found
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
TestITM
+15
-17
15 additions, 17 deletions
TestITM
examples/bare10.rs
+8
-7
8 additions, 7 deletions
examples/bare10.rs
with
23 additions
and
24 deletions
TestITM
+
15
−
17
View file @
4a3c6cae
Ok 97
Ok 471
Error 83
Error Overrun
Ok 471
Error 84
bare9
goto sleep
woken..
data 97
goto sleep
woken..
data 13
goto sleep
woken..
data 97
goto sleep
data 97
UsartReceiveOverflow
data 13
data 97
UsartReceiveOverflow
data 97
UsartReceiveOverflow
data 97
UsartReceiveOverflow
data 100
RingBufferOverflow
data 115
RingBufferOverflow
data 13
UsartReceiveOverflow
This diff is collapsed.
Click to expand it.
examples/bare10.rs
+
8
−
7
View file @
4a3c6cae
...
...
@@ -83,9 +83,9 @@ const APP: () = {
fn
trace_data
(
byte
:
u8
)
{
let
stim
=
&
mut
resources
.ITM.stim
[
0
];
iprintln!
(
stim
,
"data {}"
,
byte
);
//
for _ in 0..10000 {
//
asm::nop();
//
}
for
_
in
0
..
10000
{
asm
::
nop
();
}
}
#[task(priority
=
1
,
resources
=
[
ITM]
)]
...
...
@@ -145,15 +145,16 @@ const APP: () = {
//
// Did you loose any data (was the data correctly echoed)?
//
//
** your answer here **
//
Yes
//
// Was the data correctly traced over the ITM?
//
//
** your answer here **
//
No, it got usartrecieveoverflow
//
// Why did you loose trace information?
//
// ** your asnwer here **
// It was because of the loop that is implemented in the trace function.
// When the loop has been implemented, the function will be called again when it already is doing some work.
//
// Commit your answers (bare10_1)
//
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment