Difference between revisions of "P32 paper project"
From DIDEAS Wiki
m (→todo) |
m (→todo) |
||
Line 46: | Line 46: | ||
==todo== | ==todo== | ||
− | # | + | #thread safe / mappable printf |
+ | #mappable getchar | ||
+ | #add command timeouts in MC firmware; | ||
#make sure SC boots MC and then enters idle state | #make sure SC boots MC and then enters idle state | ||
#DMA to RX robot dataport | #DMA to RX robot dataport | ||
#DMA to TX SWIFI dataport | #DMA to TX SWIFI dataport | ||
#DMA to read ADCs | #DMA to read ADCs |
Revision as of 13:19, 8 June 2010
- BiomechDocs BL Knee PFresearchE
- Biomech Documentation links:
- AKCPU2z BLMD6c BLFT6c PSER1c Imu_2010 Emg_2009 Ric Upd_pcb
Contents
Telemetry access (PSW1, PSW2)
with SWIFI
- wifi_fast.py -i bmech4 -V ak_p32 -f xx -F
- bmech4 is access point, with lan ip 10.2.0.251, uses DMZ to route traffic.
- A 4 wire cable with pins 2,3 swapped is connected from PSW1 to the SWIFI port labeled M
- This interface is NOT isolated and can power the SWIFI
with PSER2h
- PSW1 and PSW2 are not isolated, but also do NOT provide 3.3V. The PSER2h is isolated and needs 3.3V to power the isolator. Thus it may not be possible to connect to the PSER2h without modifications
SWIFI LAN IPs
- S5 = 10.2.0.218
- S3 = 10.2.0.216
firmware architecture
P32 user level
- The state controller operates in a mid priority level thread. This means that it will interrupt lower priority threads. Before and after calling the statemachine other actions are performed:
- Receive and decode the 'dataport' message from the robot
- Populate the remote sensors objects from the DP message
- Calls the user statemachine (which can send a command to the robot)
- Sends the dataport message.
- This mid priority level thead
- The main loop is used as a background thread. At present its doing printf and actually calls ms_delay(100)!
system level
- Upon power on:
P32
- the P32 waits for the robot MC to signal "boot success";
- after which it takes control of the MC and command current mode
- then starts calling the user statemachine
MC
- waits for commands either from the SC or the P32
SC
- monitors sensors and commands MCs to commutate and retries if necessary
- on success, enters an idle state (and remains there)
todo
- thread safe / mappable printf
- mappable getchar
- add command timeouts in MC firmware;
- make sure SC boots MC and then enters idle state
- DMA to RX robot dataport
- DMA to TX SWIFI dataport
- DMA to read ADCs