Support Portenta C33 #80
Comments
|
@facchinm - Should we be trying this branch out? thanks |
|
I know I am living on the wild side... But on my secondary machine, I did clone this this branch down and also did clean install of zephyr and modules. I tried the build_all.sh it failed on the build: ./extra/build.sh ek_ra8d1 ek_ra8d1 I tried a compile a couple of simple sketches for GIGA/Portenta R7... |
|
@facchinm @pillo79 - Sorry I am sure you already know this and probably even know the fix to the above: But it appears like, changes to the file: devicetree_generated.h is causing these problems: There are lines like: Which are causing major problems for a lot of the macros that do things like: DT_FOREACH_PROP_ELEM_SEP_VARGS Before (i.e. current release this line looked like: Edit: I opened the file in SublimeText editor and did a regular expression replace operation: And now I can build blink on the Portenta H7 Edit 4: I see I had it trying to build with the debug option. I switched back to standard and now it uploads |
|
@KurtE wow, that was fast 🙂 We are cleaning up the repo a bit to move main to this branch, but before that I'm going to merge some of your PRs 😉 |
|
Regarding the macro comments build issue above - after lots of experimenting, I think I have identified the issue and fixed it in 1eade10. We will drop the Zephyr change that removes comments in the next rebase so it's one less to think about :-) |
|
@pillo79 - Thanks, Thanks again Edit: looks like I can build sketches again in the fully_linked branch |
|
I you all are busy as a one armed bandit and probably want to the UnoR4 incorporated before the next official release but wondering when you all are planning to do the next release or update fully linked since 4.1 had now been released? Might resolve some issues @KurtE and I are having Thanks |
|
@mjs513 @pillo79 @facchinm and all, Yesterday (and this morning) I thought I would do a quick test to see if I could simply say to use the released 4.1...So I updated I tried doing a: ./extra/build.sh So I looked at what was different on the Arduino zephyr project:
Those allowed most of the build for giga and H7 to complete, however I believe I have a mismatch now of which SDK version should be used: I should probably double check I am not seeing these messages with the other builds. Or maybe this is covered in one of the other updates made in the rc2 merge branch. |
|
Quick update: The error shown above was because I lost where I exported the location of the zephyr SDK.... I then tried pulling in all of the changes that were made on the beta2 branch. The build went through up to the C33 build and failed due to the: #define BV problem. I was then able to build simple sketch like blink for GIGA or portenta H7, but both fail to run: on the off chance it is the SDK version that is an issue, I will try with the older one. UPDATE: Tried setting to 16.8 and errors out: Other than that, Not sure what else to try. Update2: Found that error message was output from the ArduinoCore-zephyr project loader/main.c output: ASCII: 10820 |
|
Another update, It is now working on My Ubuntu machine... Have not tried much yet, but will. Currently seeing, if I can now reproduce this on my WIndows machine. Building under WSL, and then copy the stuff up to Rough instructions on what I am trying now on Windows machine: The build is in process... Next up will copy the build plus the tools and see if Arduino is at all happy. Will update this once I know more |
|
Sorry, I know that I am jumping the gun here, but thought it would be interesting to try to integrate up to Not sure if better to update previous comment or create a new one. Update: The debug monitor also shows the normal: usb_cdc_acm: Device suspended ... and then configured. On the Ubuntu machine, when I try the same thing on the Portenta H7, It looks like the sketch is started, However, there is no USB Serial port created: /dev/ttyACMx On my Windows machine, I was playing around with the Portenta branch, trying to integrate our changes for the current PRs, It builds, but it does not run. Different error message in Debug window: One thing I noticed on my Window's machine building the loader, at the end of the build is a different message: Looks like while generating the provides.ld file, which I believe is used in the new binding stuff... it can not find the I tried renaming this to what the build.sh file was looking for: Last attempt - I copied the overlay file to what the cat was looking for. Will check to see if I the GIGA is working sufficiently to try out the different Cameras... Need to resetup the GIGA on my Dev machine with debug setup as it still appears to be always in debug mode. (Need to enter sketch in debug window, to run) Side Note sure what the difference is between: Debug "Debug" and Debug "Standard" Now back to playing. |
|
I synched up with your repor/branch using the fully linked plus prs branch and did an build_all. Seems to be failing on the Portenta C33: all other boards seem to be building so will test with the giga and h7 lite to see what we get. UPDATE: Failing badly.
Portenta H7 UPDATE 1: Ran west upate - just in case. No change at least for Portenta H7 UPDATE 2: Re loaded everything again and inlcuded fixed for BC error which got it to build again but still no luck in getting anything to upload after burning bootloader. Doesn't appear sketch is loading as mentioned before:
UPDATE 3: Update zephyr SDK to 0.17.0 and it cleared the issue with provides.ld that I mentioned to @KurtE |
|
Ok redid the whole thing using @KurtE's fully_linked repo. Using sdk-17.0 and all changes identified in earlier posts as 16.8 had the same issues.
Now for GIGA
For H7
For Nano 33 ble sense
|
Merged
|
Not sure if comments should go here? Or new issue or issue up on zephyr... As you know, I am playing with the PR #85 have some fixes for H8, decided to play with C33. Some of it appears to work. I did not drop down into the internals section of the MBED pins. This builds, I have not tried it fully out yet. Thought I would add in UARTS, SPI, Wire objects. Which the builds fail on. I am not sure if this is it, but I believe I see an issue in the zephyr/boards/arduino/portenta_c33/arduino_portenta_c33-pinctrl.dtsi Notice the psels of these two objects are the same. will play some, but I believe that 6 object was simply copied from 5
|
|
Synched up with @KurtE's branch with his PR changes and testing on H7
|
|
C33 merged and available in released 0.3.0, will tackle @KurtE 's report and wifi support (based on zephyrproject-rtos/zephyr#87685) in the next few days. |
|
I pushed up new branch on my fork with C32 pin table stuff as well as a Draft PR. So far not getting any of the additional SCI based Serial ports working, they hang in open... Investigating. Would like to get an SPI working to the external pins, but not sure how doable that is now? The one that is implemented (have not tried to use yet, connects to ESP32, I believe. I am not seeing any implementation of SPI using SCI in the lower levels, (Zephyr or Modules). I believe the chip supports two hardware ports. With my excel document, I thought about adding the information from The RA6M5 User's Manual (about page 546...) that shows the It's not perfect, but, It helps me at least get ideas... Ths page starts off like: <style> </style>
Back to playing |
|
Hi guys, the current
|
|
Thanks @facchinm Sounds good. At some point it might help to post, or ??? about the state of some of the things that have gone into the builds. Examples: fully_linked - What does that really mean? I can guess parts of it, but does it require me to first load the bootloader or GIGA: Some of your zephyr forks, mention display shield... Is the shield working? Same software libraries as MBED or ??? WiFi/BT: supported in... using ... thanks again. |
|
pretty much have the same questions as @KurtE. |
|
I agree with you guys, the release notes are a bit lacking at the moment, but we'll try to get better 🙂 |
|
Here we go https://github.com/arduino/ArduinoCore-zephyr/wiki/%5B250331%5D-Project-status-%E2%80%90-release-0.3.0 . Hopefully since it's a wiki we can use the compatibility matrix to keep track of the various activities (feel free to modify the page of course 🙂 ) |
Thanks @facchinm that should help a alot |
|
Thanks @facchinm Helps a lot. A quick answer to myself about could I define another SPI object for SPI0...
I don't think it would work very well: MISO0 - D13 (could use), D41 (Used for CAN, most breakouts appear to only show after going through CAN ... D109 - Ethernet stuff |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
WIP branch: https://github.com/arduino/ArduinoCore-zephyr/tree/fully_linked
Stopping issues: zephyrproject-rtos/mbedtls#68
The text was updated successfully, but these errors were encountered: