michallenc commented on issue #3765:
URL: 
https://github.com/apache/incubator-nuttx/issues/3765#issuecomment-859384707


   Hello all,
   
   the first week of GSoC coding period is about to end and I´d like to refer 
about the progress we made during the first week and during pre coding period.
   
   During pre GSoC period I extended pysimCoder CAN support for NuttX with 
SocketCAN support so pysimCoder now supports both characteristic device 
dev/can0 and socketcan. This was [integrated into pysimCoder mainline last 
week](https://github.com/robertobucher/pysimCoder/pull/6). This week was mainly 
about incremental encoder and DC motor control, which has been done on STM32 
Nucleo F446RE and presented to the mentors during our weekly meeting. DC motor 
control required support for GPIO driver for Nucleo F446RE which was 
implemented to NuttX in [PR 3880 
](https://github.com/apache/incubator-nuttx/pull/3880). This implementation 
also required [new pysimCoder block for relational 
operation](https://github.com/robertobucher/pysimCoder/commit/5c7c49188018f9292e2e005f2c62f3ab471049e3).
   
   The main platform of the project is iMXRT 1060 MCU so the goal is also to 
get the DC motor control running there, but I am currently having some troubles 
with encoder driver for imxrt. I already did some fixes to xbar driver (added 
missing clock), but still some work is to be done in encoder driver (as it 
stands now, the driver registers the device but do not update the position 
value).
   
   Yesterday I created a wiki page about the project on pysimCoder git. We 
agreed during the meeting that the goal would be to store links to commits to 
pysimCoder and NuttX there as well as the content of our meetings. [The page 
can be found 
here](https://github.com/robertobucher/pysimCoder/wiki/GSoC-2021:-pysimCoder-integration-with-NuttX).


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to