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

ARM Cortex-M3 support? #385

Open
canDry opened this issue Feb 10, 2021 · 10 comments
Open

ARM Cortex-M3 support? #385

canDry opened this issue Feb 10, 2021 · 10 comments

Comments

@canDry
Copy link

canDry commented Feb 10, 2021

I'm trying to get PJON working on an arduino DUE (ARM Cortex-M3).

Although there's no errors in compilation the network test never connects with ans ESP32 receiver (it works successfully when the sender is an arduino uno on pin 12). I've tried various pins (12, 25, 52) with no luck.

Is there support for this board?

Cheers!

@gioblu
Copy link
Owner

gioblu commented Feb 11, 2021

Ciao @canDry :)
Take a look here: https://github.com/gioblu/PJON/blob/master/src/strategies/SoftwareBitBang/Timing.h#L207
This is the timing configuration of ESP32, we do not have a dedicated setup for Arduino DUE, although if you already see even few successful exchanges that means a slight tweak will likely yield optimal performance.

Please see: https://github.com/gioblu/PJON/wiki/SoftwareBitBang-troubleshooting

@canDry
Copy link
Author

canDry commented Feb 11, 2021

Take a look here: https://github.com/gioblu/PJON/blob/master/src/strategies/SoftwareBitBang/Timing.h#L207

Thanks for the quick response Gio!

Was hoping perhaps someone will see this - and has the timing worked out - but never bothered w/ a pull request. 😎

@gioblu
Copy link
Owner

gioblu commented Feb 12, 2021

Ciao @canDry it is probably the time for me to buy an Arduino DUE, I will let you know how my tests go.

@canDry
Copy link
Author

canDry commented Feb 12, 2021

I have a cheap DSO-138 oscilloscope.... do you think that would be sufficient for me to diagnose/tune the timing?

Regardless, if you actually purchase a DUE to solve this issue and you fall into the relatively-poor open-source-developer camp send me a copy of the bill and I'll reimburse you via paypal. :)

Cheers!

@gioblu
Copy link
Owner

gioblu commented Feb 13, 2021

@canDry I don't think you need an oscilloscope to find the right timing it you already get some packets through. Try changing SWBB_READ_DELAY on due side and see if results are better, it may be just that setting a slightly higher or lower SWBB_READ_DELAY, in the worst case SWBB_BIT_WIDTH should be tuned too, and in that case an oscilloscope may help, probably the DSO-138 is more than enough.

@gioblu
Copy link
Owner

gioblu commented Feb 13, 2021

Ah @canDry about the DUE purchase, don't be preoccupied it is some time I had in mind to test that MCU, and that is not a huge expense, just too many things on the list :)

@gioblu
Copy link
Owner

gioblu commented Feb 13, 2021

@canDry I bought also the chinese ebay clone for less then 15 dollars, curious to know if behaves the same. Do you have the real or the clone?

@canDry
Copy link
Author

canDry commented Feb 13, 2021

@canDry real or the clone?

Mine is from Sainsmart - so a clone.

If I get some time this weekend, I'll try playing with the #define SWBB_READ_DELAY +/- to see if I can get the DUE talking to the ESP32.

Thanks again for your prompt and very helpful response (as usual!).

@gioblu
Copy link
Owner

gioblu commented Mar 11, 2021

Ciao @canDry I finally have my Due and some time to try! I will let you know in the next days.

@fletchjp
Copy link

Is there any progress on this? I have connected two DUEs using SoftwareBitBang and get no connection. I cannot see anything in the Timing.h file which relates to a DUE. I don't know enough to know what to add.

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

No branches or pull requests

3 participants