Skip to content

New mbed platform VK_RZ_A1H #1639

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

Merged
merged 1 commit into from
Apr 29, 2016
Merged

New mbed platform VK_RZ_A1H #1639

merged 1 commit into from
Apr 29, 2016

Conversation

mbedNoobNinja
Copy link
Contributor

These are the sources for development kit VK-RZ/A1H V4.0

  • default NET tests don't pass when compiled with GCC_ARM toolchain, because there is some issue with function rtos_idle_loop(), although it physically exist in rtos library and more specifically in file rtos_idle.c. However If you specify "-Wl,--unresolved-symbols=ignore-in-object-files" flag in the link command in gcc.py, they pass.
  • CAN loopback & analog pot tests may don't pass at first time (especially if they are tested along with other tests), but they always pass if they are tested alone.
  • None of the export scripts are ready yet, because of too rookie python scripting skills and limited toolchain's projects template knowledge. Let the more knowledgeable people feel free to write them

@0xc0170
Copy link
Contributor

0xc0170 commented Mar 31, 2016

None of the export scripts are ready yet, because of too rookie python scripting skills and limited toolchain's projects template knowledge. Let the more knowledgeable people feel free to write them

You just need to add a target definition : https://github.com/project-generator/project_generator_definitions/ (find there targets.py). RZ_A1H mcu is already supported for IAR.

default NET tests don't pass when compiled with GCC_ARM toolchain, because there is some issue with function rtos_idle_loop(), although it physically exist in rtos library and more specifically in file rtos_idle.c. However If you specify "-Wl,--unresolved-symbols=ignore-in-object-files" flag in the link command in gcc.py, they pass.

@TomoYamanaka Have you had any problems with GCC ARM and net libraries?

@mbedNoobNinja
Copy link
Contributor Author

If the sources are built and linked as they are (without modification) GCC linker is not happy & complains:

C:\Projects\kitVKRZA1H\sw\mbedmicro\SDK\build\rtos\TARGET_VK_RZ_A1H\TOOLCHAIN_GCC_ARM\librtx.a(RTX_Conf_CA.o): In function os_idle_demon': RTX_Conf_CA.c:(.text.os_idle_demon+0x0): undefined reference tortos_idle_loop'
collect2.exe: error: ld returned 1 exit status
[16:15:32] Error: There were errors while building project NET_1

but if you modify the line in gcc.py to look like this, linker is OK

self.ld = [join(tool_path, "arm-none-eabi-gcc"), "-Wl,--gc-sections", "-Wl,--wrap,main", "-Wl,--unresolved-symbols=ignore-in-object-files"] + self.cpu

with_modified_gcc_py.txt, with_untuched_gcc_py.txt

I don't know who should provide this rtos_idle_loop() function and why the other toolchains haven't
this problem ?

@TomoYamanaka
Copy link
Contributor

Hi

default NET tests don't pass when compiled with GCC_ARM toolchain, because there is some
issue with function rtos_idle_loop(), although it physically exist in rtos library and more specifically
in file rtos_idle.c. However If you specify "-Wl,--unresolved-symbols=ignore-in-object-files" flag in
the link command in gcc.py, they pass.

@TomoYamanaka Have you had any problems with GCC ARM and net libraries?

The same phenomenon (default NET tests don't pass when compiled with GCC_ARM toolchain) has occurred here.
When we tested in the past, there was no problem.
It might be the following change is affecting.
#1597
It seems rtos_idle_loop() has been added in this pull request.
We tried in the LPC1768, but the same phenomenon has occurred.

Regars,
Yamanaka

@0xc0170
Copy link
Contributor

0xc0170 commented Apr 1, 2016

Thanks guys for providing more info. Neil already replied to that PR introducing idle loop, will be fixed. Apart from this, @mbedNoobNinja can you share the test results here? (run singletest.py - the basic tests)

cc @screamerbg

@mbedNoobNinja
Copy link
Contributor Author

Ok here they are:
TEST_SUMMARY.txt

@0xc0170
Copy link
Contributor

0xc0170 commented Apr 4, 2016

Thanks for sharing the tests results.

@0xc0170
Copy link
Contributor

0xc0170 commented Apr 12, 2016

@mbedNoobNinja I locally resolved the conflicts, but can't merge it because we need CLA.

Can you please sign https://developer.mbed.org/contributor_agreement/, and share your nick on mbed.org. Thanks

@mbedNoobNinja
Copy link
Contributor Author

Ok. The agreement in question has been signed by the name of tvendov and this form has been filled. The 10 hardware samples will be shipped soon (may be next week, I hope). That's for now. Thanks for the help.

@screamerbg
Copy link
Contributor

@0xc0170 @mbedNoobNinja boards received at ARM and test results confirmed

Thanks

@0xc0170
Copy link
Contributor

0xc0170 commented Apr 22, 2016

@mbedNoobNinja Can you please rebase your branch?

@mbedNoobNinja
Copy link
Contributor Author

Ok branch is rebased

@0xc0170
Copy link
Contributor

0xc0170 commented Apr 26, 2016

Thank you, I'll merge this within a day

@0xc0170 0xc0170 merged commit 670e7bc into ARMmbed:master Apr 29, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants