Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is it possible to clear Uart in azure #264

Open
nishithpoojary opened this issue Jun 30, 2023 · 5 comments
Open

Is it possible to clear Uart in azure #264

nishithpoojary opened this issue Jun 30, 2023 · 5 comments

Comments

@nishithpoojary
Copy link

nishithpoojary commented Jun 30, 2023

Hi. I have to send some hex values through uart. But I noticed even after the data is sent , when I send next set of hex values it had some unwanted values.
example :- data to be sent 02 04 01 00
data received by FTDI connected to azure : E0 02 04 01 00
I don't understand how a extra byte E0 (this value changes) is received by FTDI.

Please guide me on this issue. Thank you.

@jamesadevine
Copy link
Contributor

is E0 received after resetting the board or while the application is running?

@nishithpoojary
Copy link
Author

While the application is running itself I faced this issue. Even after erasing the azure board and tried deploying I faced this issue.

@jamesadevine
Copy link
Contributor

I doubt the board is actually sending this data intentionally. Try flushing the FTDI buffers before you try and read from the device.

@nishithpoojary
Copy link
Author

nishithpoojary commented Jun 30, 2023

Its the same when i use nrf board connected to azure. A specific hex value is required by nrf to do its work. But since the nrf doesn't receive this proper hex value, the nrf stays idle waiting for required hex value.

@jamesadevine
Copy link
Contributor

I think more context is required here. I'll reach out to you over email to arrange a time to talk.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants