Skip to content
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

ports/renesas-ra: Ehternet support for VK-RA6M5 #12047

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

mbedNoobNinja
Copy link
Contributor

Now VK-RA6M5's hardware can take advantage of the existing lwIP support in uPy.

Other renesas bords can also use it, as long as their PHY chip is the same as VK's one i.e (ICS1894). If not, a minor changes in the FSP config files, can allow usage of one that is supported by the FSP itself.

@TakeoTakahashi2020
Copy link
Contributor

Using VK-RA6M5, I confirmed build and execution as below. It's woking fine.

Build:

make -C mpy-cross
cd ports/renesas-ra
make submodules
(cd ../..; git submodule update --init lib/mbedtls lib/lwip)
make BOARD=VK_RA6M5

Execution:

import network
import socket
lan = network.LAN()
lan.active(True)
addr = socket.getaddrinfo('micropython.org', 80)[0][-1]
s = socket.socket()
s.connect(addr)
s.send(b'GET / HTTP/1.1\r\nHost: micropython.org\r\n\r\n')
s.settimeout(1.0)
while True:
    try:
        data = s.readline()
    except Exception as e:
        if str(e) == "[Errno 110] ETIMEDOUT":
            break
        print(e)
    else:
        print(data)
s.close()
lan.active(False)

@mbedNoobNinja
Copy link
Contributor Author

After rebasing M5 can now take advantage of recently added tinyUSB support (thanks to @iabdalkader). Ethernet support is also synced with recently enabled lwIP for C33 board. M5's External Octa RAM can now be used by uPy.

Signed-off-by: mbedNoobNinja <novoltage@gmail.com>
@projectgus
Copy link
Contributor

This is an automated heads-up that we've just merged a Pull Request
that removes the STATIC macro from MicroPython's C API.

See #13763

A search suggests this PR might apply the STATIC macro to some C code. If it
does, then next time you rebase the PR (or merge from master) then you should
please replace all the STATIC keywords with static.

Although this is an automated message, feel free to @-reply to me directly if
you have any questions about this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants