-
-
Notifications
You must be signed in to change notification settings - Fork 14
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
Initial Portenta C33 testing using 0.3.0 #93
Comments
The problem reported as
is related to the missing hook for 1200bps touch on USB_DEVICE_NEXT devices (for now, only the C33). I2C problem is very likely due to the not found addresses during scan() WIll take a look at the other issues in the next days |
I was curious about this, so took a look at it. If my quick look at the MBED sources is correct, most
So I am guessing maybe it just uses DTR to reboot? Or other mechanism? Looking through zephyr code (and forum posts), I don't believe there is any callbacks for when DTR changes |
On the Renesas core we use dfu-runtime infrastructure to trigger the reset 😉 |
Thanks, it looked like you have the 1200... hook defined in the variant.cpp file. And I put in printk statement into I noticed in the config fies, that most of the others had the .conf file define of: EDIT: When I do try to program the C33, there is a 1200 BPS I added the printk:
And I am seeing:
And as I suspected, I am not seeing those message from Portenta H7 build. |
More updates on trying to get SerialX to work. I have a hacked up version of the SerialPassthrough example sketch, where I am also printing up some start up data...
I am still having issues with Serial2... Have not tried Serial1 as being used as console But today I have had success talking to Serial3 and Serial4. Will check Serial2 again. On Serial2, it was hanging in the low level module. R_SCI_UART_Open right after the interrupts were
*** Booting Zephyr OS build v4.1.0-901-g666b48e54479 ***
Print Port/Pin Function Select
|
Update: Serial2 appears to be working as well. Wonder if Serial1 and 2 are reversed in my list... That is the debug actually goes out on Serial2? Thought I would see how it all works with each other, so I did a quick and dirty update to one of the tests I
Short answer looks like it is losing data...
Will check this out later. Already works better than some of the others... |
@facchinm - wondering about code versus schematic for C33 for Serial ports...
From Variant.cpp
Back to the schematic:
And the one I have not added yet but MBED: as guessing you might be using the other device tree stuff you added, but could easily |
@facchinm @pillo79 - Sorry for asking lots of questions. I think I may mark my current C33 PR as ready to merge although was looking at the Wire objects. MBED defines 4 of them, whereas we only have one.... Currently on the Zephyr side we only define:
And in the DTS we have
So I was going to define the iic0 object in the overlay...
And 91-94 have 0x78-0x7B, which from the RM tables I see: But my guestion is, who decides that slots 91-94 are the proper ones to use? How many others are hard coded? Can the build simply allocate unused ones for this? Or is it done just to make it easy for a library, to not have to look it up? |
Quick update: Not sure about Wire2 yet as it is SCI2 Also like Serial, not sure about WIre3 yet as it is SCI3 and is internal ... But looks like it works. I tested it using Sparkfun QWIIC buttons, one on Wire and the other on Wire1. One hook up was Pardon the mess as my table/desk has several different hookups and this one alone has the ones mentioned plus USB to Serial |
Not sure you want individual issues but this is what I am seeing so far.
Blink:
Hangs Serial in debug and standard modes. Nothing on Serial1
Thread_Create:
Looses Serial with following error on Serial1 in debug or standard mode:
I2C:
Scanner works but keep seeing error on Serial1
Ran the BMI270 sparkfun library on wire and that seems to be working no issue. Not seeing the spew which is good.
SPI:
Not implemented yet
Note: keep having to put it into boot mode to load a sketch but maybe thats just the previous sketch that is being run.
The text was updated successfully, but these errors were encountered: