You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+11-3Lines changed: 11 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,11 +10,11 @@ The main project also uses code from **dbprint**, this needs to be added alongsi
10
10
11
11
## 1 - GIT repo structure
12
12
13
-
### 1.1 - code/SLSTK3400A_blink-unoptimized
13
+
### 1.1 - code/SLSTK3400A_blink-unoptimized/
14
14
15
15
This is an un-optimized **blink** example which was created at the start of the lab sessions to get to know *Simplicity Studio*. The code created here is referenced in [this report](doc/reports/EmbeddedDesign1-labo1-2-BrechtVanEeckhoudt-ChrisThoen.pdf) (Dutch).
16
16
17
-
### 1.2 - code/SLSTK3400A_blink-optimized
17
+
### 1.2 - code/SLSTK3400A_blink-optimized/
18
18
19
19
This is an optimized **blink** example which was created at the start of the lab sessions to get to know *Simplicity Studio*. The code created here is referenced in [this report](doc/reports/EmbeddedDesign1-labo1-2-BrechtVanEeckhoudt-ChrisThoen.pdf) (Dutch).
20
20
@@ -26,7 +26,7 @@ This is the main code developed for the project for the lab sessions. This is wh
26
26
27
27
## 2 - Documentation
28
28
29
-
**The following documentation is all about**`code/SLSTK3400A_ADXL362`.
29
+
**The following documentation is all about**`code/SLSTK3400A_ADXL362/`.
30
30
31
31
<br/>
32
32
@@ -109,10 +109,14 @@ We first left `automatic ChipSelect` in the `USART config` enabled. After gettin
109
109
110
110
**As seen above, the ChipSelect pin goes low for each byte. This is not the correct behaviour, since it needs to stay low for three bytes** (`register address`- `read/write` - `value to read/write`).
111
111
112
+
<br/>
113
+
112
114
After manually setting the CS pin high and low we got the correct behaviour, as depicted below.
The same behaviour was observed when we tried to *read a register*. The first picture below is the incorrect behaviour, afterwards we see the accelerometer responding correctly.
0 commit comments