Not applicable
Apr 03, 2014
08:11 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Apr 03, 2014
08:11 AM
3 Replies
Not applicable
Apr 08, 2014
01:43 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Apr 08, 2014
01:43 AM
Hi Doug,
In the latest UART001 [1.0.22], the “Pin Configuration” option has been removed from UI. Hence, user is unable to configure input/output characteristic for Rx/Tx pin.
The main purpose is to avoid wrong configuration since most of the common use cases have been taken care by DAVE.
Best regards,
Sophia
In the latest UART001 [1.0.22], the “Pin Configuration” option has been removed from UI. Hence, user is unable to configure input/output characteristic for Rx/Tx pin.
The main purpose is to avoid wrong configuration since most of the common use cases have been taken care by DAVE.
Best regards,
Sophia
Not applicable
Apr 08, 2014
05:34 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Apr 08, 2014
05:34 AM
Sophia,
Thank you for the clarification.
Is there any future intent to document what common use cases DAVE covers.
This will help clarify what DAVE does, but more importantly what DAVE doesn't do.
For example, many of the peripherals supported in DAVE can be configured for various use cases, but DAVE only supports a few of those configurations.
It would be helpful to know if the missing configurations are not considered common or will be added in a future release.
This will help users determine when they should write drivers on top of DAVE, write their own drivers, or ask for clarification on DAVE functionality.
Regards,
Doug
Thank you for the clarification.
Is there any future intent to document what common use cases DAVE covers.
This will help clarify what DAVE does, but more importantly what DAVE doesn't do.
For example, many of the peripherals supported in DAVE can be configured for various use cases, but DAVE only supports a few of those configurations.
It would be helpful to know if the missing configurations are not considered common or will be added in a future release.
This will help users determine when they should write drivers on top of DAVE, write their own drivers, or ask for clarification on DAVE functionality.
Regards,
Doug
Not applicable
Apr 08, 2014
10:26 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Apr 08, 2014
10:26 PM
Hi Doug,
Thank you very much for the feedback. I'll help to forward this to the responsible person.
Best regards,
Sophia
Thank you very much for the feedback. I'll help to forward this to the responsible person.
Best regards,
Sophia