Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
M
multipass
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
Package registry
Model registry
Operate
Environments
Terraform modules
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
derf
multipass
Commits
b3451dad
Commit
b3451dad
authored
5 years ago
by
Daniel Friesel
Browse files
Options
Downloads
Patches
Plain Diff
transactiontest: MSP430FR5994, avoid inturrupt issues
parent
905fc53c
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
src/app/transactiontest/util.S
+5
-4
5 additions, 4 deletions
src/app/transactiontest/util.S
with
5 additions
and
4 deletions
src/app/transactiontest/util.S
+
5
−
4
View file @
b3451dad
...
...
@@ -3,7 +3,7 @@
.
global
asm_load_mem
#define SRAM_BASE #1c00h
#define SRAM_SIZE
2048
#define SRAM_SIZE
4096
; SRAM backup space
sram_backup
:
...
...
@@ -74,11 +74,12 @@ asm_load_all:
pop
r11
ret
dint
do_load_all
:
; restore SRAM from backup
mov
#
sram_backup
,
r10
mov
SRAM_BASE
,
r11
dint
load_sram_word
:
mov
@
r10
+,
0
(
r11
)
add
#
2
,
r11
...
...
@@ -108,9 +109,10 @@ asm_load_mem:
cmp
#
1234
h
,
r11
jeq
do_load_mem
pop
r11
eint
ret
dint
do_load_mem
:
push
r10
push
r9
...
...
@@ -119,7 +121,6 @@ do_load_mem:
mov
r1
,
r9
mov
#
sram_backup
,
r10
mov
SRAM_BASE
,
r11
dint
load_sram_word2
:
mov
@
r10
+,
0
(
r11
)
add
#
2
,
r11
...
...
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