-
Notifications
You must be signed in to change notification settings - Fork 3k
Update for VK_RZ_A1H #6245
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
Update for VK_RZ_A1H #6245
Conversation
@TomoYamanaka, if you could also take a look at this PR, that would be great. |
@mbedNoobNinja It looks like there were a lot of changes that went into this PR. Could you clarify what you mean by "synced with mbed-os 5.7.6"? |
I mean after a bug was introduced in issue № (#5777), this is the supposed fix that should resolve that issue. In short the last working mbed-os for the platform VK_RZ_A1H was 5.4.7 and there was no Cortex A9 support then. But since the maintenance is already a fact with 5.6.0, and there were some drastic changes in folder's structure as whole (#4440) and so on, ... update was needed. Now VK_RZ_A1H is "aligned" with GR_PEACH (RZ_A1H) & GR_LYCHEE (RZ_A1LU) and VK_RZ_A1H should be compilable with 5.6.x and above. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you extend the commit message, and describe what's actually going on. Something like in your last comment. Also you are adding release_version: [2, 5]
to VK_RZ_A1H so that's a basically new board support as it was not active before.
@@ -31,6 +31,7 @@ | |||
|
|||
|
|||
|
|||
#define TRANSACTION_QUEUE_SIZE_SPI 16 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you delete the unnecessary empty lines.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.
@bulislaw Is the updated commit message a bit better? |
Sorry for late reply. I think that it is okay regarding the changed code. |
After I read the referenced issue above (#5777) that I created earlier, I understand the changes here. This target was disabled as it was out of sync with other Renesas targets. This PR is updating the codebase, aligning it with the rest of the targets and thus reenabling it back to 2 and 5 (thus that release version). @mbedNoobNinja it's always good to describe briefly at least changes even if reference is provided (that came later ,thanks!). Can you amend you commit message to contain these details? What update is it -
This info is crucial here |
Yeah. The commit message became a little longer ... |
That is why there is a commit message, can be few paragraphs long if it needs to be. I find it now more clear (note that first line should be the most 50 characters, as you can see how it wraps here). |
@mbedNoobNinja Looking at the test results, some of the networking tests fail? Can you please clarify. |
Yes, the Ethernet functions very well, ( at least the sockets -> I managed to receive video RTSP stream on mbed through both: UDP & TCP) even though these 3 tests
always fails, and I don't know why. Even in OS 5.4.7 Perhaps this is an Internet provider related issue, I don't know. |
@TomoYamanaka Are you aware of these issues, are they reproducible ? we shall take them to a separate issue. This PR does not touch networking code. Shall ethernet be disabled until it's fixed? |
@0xc0170 |
/morph build |
Build : FAILUREBuild number : 1397 |
@mbedNoobNinja Please review the ARMCC build problem |
Hm strange. With mbed CLI it is compiled successfully (blinky example). |
I can not reproduce the problem. I fetched your branch locally, build the sermaphore test without any error (I am using locally armcc 5.06 update 5 at the moment) @studavekar Can you reproduce the build failure here? /morph build |
Build : FAILUREBuild number : 1417 |
Locally |
Mbed-os 5.4.7 was the last unofficial working support for this target. Since Mbed-os 5.6.0, the support is now official and VK_RZ_A1H is now "codebase aligned" with GR_PEACH (RZ_A1H) & GR_LYCHEE (RZ_A1LU) !
Found the problem |
🙌 /morph build |
Build : SUCCESSBuild number : 1486 Triggering tests/morph test |
Exporter Build : SUCCESSBuild number : 1131 |
Test : SUCCESSBuild number : 1273 |
/morph mbed2-build |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All prior comments were addressed, and looks like the only change outside of TARGET_RENESAS was targets.json.
👍
Description
Platform VK_RZ_A1H synced with mbed-os 5.7.6
Test Rezults:
VK_RZ_A1H_ARM_TESTs.log
VK_RZ_A1H_GCC_TESTs.log
VK_RZ_A1H_IAR_TESTs.log
Pull request type