nanoFramework.IoT.Device icon indicating copy to clipboard operation
nanoFramework.IoT.Device copied to clipboard

Add BlueNrg2

Open KasperJSdeVries opened this issue 3 years ago • 7 comments

Description

Motivation and Context

How Has This Been Tested?

Not yet

Screenshots

Types of changes

  • [ ] Improvement (non-breaking change that improves a feature, code or algorithm)
  • [ ] Bug fix (non-breaking change which fixes an issue with code or algorithm)
  • [x] New feature (non-breaking change which adds functionality to code)
  • [ ] Breaking change (fix or feature that would cause existing functionality to change)
  • [ ] Config and build (change in the configuration and build system, has no impact on code or features)
  • [ ] Dependencies (update dependencies and changes associated, has no impact on code or features)
  • [ ] Unit Tests (add new Unit Test(s) or improved existing one(s), has no impact on code or features)
  • [ ] Documentation (changes or updates in the documentation, has no impact on code or features)

Checklist:

  • [ ] My code follows the code style of this project (only if there are changes in source code).
  • [ ] My changes require an update to the documentation (there are changes that require the docs website to be updated).
  • [ ] I have updated the documentation accordingly (the changes require an update on the docs in this repo).
  • [ ] I have read the CONTRIBUTING document.
  • [ ] I have tested everything locally and all new and existing tests passed (only if there are changes in source code).
  • [ ] I have added new tests to cover my changes.

KasperJSdeVries avatar May 31 '22 08:05 KasperJSdeVries

According to the build there are currently 699 public-facing things that need to be commented. I think it would be best if we minimize the interface as much as possible. The main way I see us do that is by integrating it with the nanoFramework.Device.Bluetooth package.

KasperJSdeVries avatar May 31 '22 11:05 KasperJSdeVries

This Implementation is currently dependent on SPI getting manual support

KasperJSdeVries avatar Jun 01 '22 08:06 KasperJSdeVries

Should this device support both nanoFramework.Device.Bluetooth and manual implementation?

KasperJSdeVries avatar Jul 12 '22 08:07 KasperJSdeVries

@KasperJSdeVries, now a lot of things has been moving on the Bluetooth side, any chance to move this one further?

Ellerbach avatar Aug 22 '22 11:08 Ellerbach

@Ellerbach I am working on this. I am however running into some issues when trying to test it. Once I fix those I will be having a look at the new bluetooth features. The bluetooth-IoT interface still needs to be decided. once that is there it shouldn't take much to fully integrate it.

KasperJSdeVries avatar Aug 22 '22 12:08 KasperJSdeVries

I realise this is a draft and subject to change... but thought I would add the need to keep the .nuspec files inline for sucessful CI...

image

networkfusion avatar Aug 25 '22 21:08 networkfusion

I realise this is a draft and subject to change... but thought I would add the need to keep the .nuspec files inline for sucessful CI...

The reason the Build is failing is because of the large part of the API that hasn't been documented yet.

KasperJSdeVries avatar Aug 26 '22 07:08 KasperJSdeVries

Hey @KasperJSdeVries are you still working on this?

josesimoes avatar Dec 19 '22 08:12 josesimoes