-
-
Notifications
You must be signed in to change notification settings - Fork 212
MKRRGB Doesn't Compile #16
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
Comments
|
OK - but Potenta has "MKR" compatible pin assignments and MKR compatible connectors, correct? I've been trying to get that to work - and maybe if this isn't 100% compatible it could explain some issues I've seen with Serial1. Thanks, |
The MKR connector are compatible on the 1st level of functionality (SPI, I2C, Serial, analog and gpios), not on the additional mux functionality that depend on the particular microcontroller in use. |
From the ST datasheet - it looks like A3 can be configured as a SPI output: For serial1 - I have a sketch where this worked fine:
Now the function looks like this to get it not to time out or get hung:
At least I had to do that to make any progress - Serial1 was getting hung. This worked fine with the previous MKR boards - Vidor, Nano 33 IoT, WiFi 1010. Regards, |
None of the pins wired to the RGD shield are capable of outputting an SPI clock, which is needed for the functionality. |
This sketch works fine in my configuration
It prints
if I press any key except 'E' and
if I keep pressing it. |
Do you happen to have one of these by any chance:? I can provide the demo sketch for that since I'm communicating with one of those. Regards, |
OK - I'll run your sketch and report back then. For the LDM-6432, it will send an 'E' command when a string command is completed; just so that's clear. |
Does this work OK for you: // command to write string to Lumex LDM-6432 display Thanks, |
Unfortunately not; but using the second function you sent me I get a print of "test" every time I press 'E' (which is the expected behavior reading the sources) |
OK - I hope something isn't going on electrically so to speak with the Portenta I have on Serial1. I'm going to hook up an external FTDI/USB I/F to Serial1 and see if I can duplicate your results. It may take a little while to get back - I need to build a little harness to get a Serial1 terminal going. Another quick question - does the Portenta run a little hot? Thanks! |
Yup, I'm testing with an FTDI, so the issue could be electrical. |
Definitely interested in the beta phase... Will let you know if I see something electrically with my board - sure hope not but I could have done something maybe... Thanks! |
Martino, Ah, is Serial1 a designated debug port? I'm getting this after hooking up the FTDI I/F - this will definitely goof up the LDM-6432...
Thanks, |
It is, totally my fault not to think that you were using WiFi too. |
No problem Martino. Yes - this was at the top: Ah, can it be something we can turn on/off with a #define or maybe a compile switch? It's kindof handy looking at the AP scan and all. Are we going to be able to make custom builds for the Murata WiFi like the ESP32 BTW??? Thanks! |
Unfortunately the WHD driver for Murata module (that comes with a precompiled and closed source firmware 😞 ) is part of mbed buildsystem, so the log can't be enabled and disabled from the sketch side (although we could patch it to expose such functionality). |
I added a way to retrieve the logs and print them on demand; the explanation is here #18 (comment) 😉 |
Martino, Using the branch for wifi_nolog - Serial1 seems to be fine now. Does the debugger work yet with the Portenta? I guess you have to have a .json file for that like for Visual Code debug, right? Thanks! |
Martino, Does this work with the nolog branch or the 'base'?
With the nolog branch I'm getting:
Thanks, |
The |
Martino, I've been able to start the debugger using the ThreadDebug lib as in the example/sketch - was able to get to the first breakpoint but then I guess it disconnects for some reason; but this is progress. Thanks, |
@jwestmoreland If you want, you can open a separate issue on the ThreadDebug issue and I can try to help solve it. |
OK Adam: https://github.com/arduino/ArduinoCore-mbed/issues/19 added. Thanks, |
To Reproduce:
In an portenta_m7 sketch:
Regards,
John W.
The text was updated successfully, but these errors were encountered: