2020-01-20 11:25:51 +00:00
|
|
|
/*
|
|
|
|
* This file is part of the MicroPython project, http://micropython.org/
|
|
|
|
*
|
|
|
|
* The MIT License (MIT)
|
|
|
|
*
|
|
|
|
* Copyright (c) 2019 Damien P. George
|
|
|
|
* Copyright (c) 2020 Jim Mussared
|
|
|
|
*
|
|
|
|
* Permission is hereby granted, free of charge, to any person obtaining a copy
|
|
|
|
* of this software and associated documentation files (the "Software"), to deal
|
|
|
|
* in the Software without restriction, including without limitation the rights
|
|
|
|
* to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
|
|
|
* copies of the Software, and to permit persons to whom the Software is
|
|
|
|
* furnished to do so, subject to the following conditions:
|
|
|
|
*
|
|
|
|
* The above copyright notice and this permission notice shall be included in
|
|
|
|
* all copies or substantial portions of the Software.
|
|
|
|
*
|
|
|
|
* THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
|
|
* IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
|
|
* FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
|
|
|
* AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
|
|
* LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
|
|
* OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
|
|
|
|
* THE SOFTWARE.
|
|
|
|
*/
|
|
|
|
|
|
|
|
#include "py/runtime.h"
|
2021-05-07 14:21:09 +01:00
|
|
|
#include "py/stream.h"
|
2020-01-20 11:25:51 +00:00
|
|
|
#include "py/mphal.h"
|
2021-07-09 05:19:15 +01:00
|
|
|
#include "shared/timeutils/timeutils.h"
|
2022-03-27 07:50:34 +01:00
|
|
|
#include "shared/runtime/interrupt_char.h"
|
2021-07-03 17:39:17 +01:00
|
|
|
#include "extmod/misc.h"
|
2021-05-16 04:27:54 +01:00
|
|
|
#include "ticks.h"
|
2020-01-20 11:25:51 +00:00
|
|
|
#include "tusb.h"
|
2021-06-13 15:42:19 +01:00
|
|
|
#include "fsl_snvs_lp.h"
|
2021-12-18 20:16:07 +00:00
|
|
|
|
2022-03-27 07:50:34 +01:00
|
|
|
#ifndef MICROPY_HW_STDIN_BUFFER_LEN
|
|
|
|
#define MICROPY_HW_STDIN_BUFFER_LEN 512
|
2021-12-18 20:16:07 +00:00
|
|
|
#endif
|
2020-01-20 11:25:51 +00:00
|
|
|
|
|
|
|
#include CPU_HEADER_H
|
|
|
|
|
2022-03-27 07:50:34 +01:00
|
|
|
STATIC uint8_t stdin_ringbuf_array[MICROPY_HW_STDIN_BUFFER_LEN];
|
2021-07-03 17:39:17 +01:00
|
|
|
ringbuf_t stdin_ringbuf = {stdin_ringbuf_array, sizeof(stdin_ringbuf_array), 0, 0};
|
|
|
|
|
2022-03-27 07:50:34 +01:00
|
|
|
uint8_t cdc_itf_pending; // keep track of cdc interfaces which need attention to poll
|
2020-01-20 11:25:51 +00:00
|
|
|
|
2022-03-27 07:50:34 +01:00
|
|
|
void poll_cdc_interfaces(void) {
|
|
|
|
// any CDC interfaces left to poll?
|
|
|
|
if (cdc_itf_pending && ringbuf_free(&stdin_ringbuf)) {
|
|
|
|
for (uint8_t itf = 0; itf < 8; ++itf) {
|
|
|
|
if (cdc_itf_pending & (1 << itf)) {
|
|
|
|
tud_cdc_rx_cb(itf);
|
|
|
|
if (!cdc_itf_pending) {
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
2020-01-20 11:25:51 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
|
2022-03-27 07:50:34 +01:00
|
|
|
void tud_cdc_rx_cb(uint8_t itf) {
|
|
|
|
// consume pending USB data immediately to free usb buffer and keep the endpoint from stalling.
|
|
|
|
// in case the ringbuffer is full, mark the CDC interface that need attention later on for polling
|
|
|
|
cdc_itf_pending &= ~(1 << itf);
|
|
|
|
for (uint32_t bytes_avail = tud_cdc_n_available(itf); bytes_avail > 0; --bytes_avail) {
|
|
|
|
if (ringbuf_free(&stdin_ringbuf)) {
|
|
|
|
int data_char = tud_cdc_read_char();
|
|
|
|
if (data_char == mp_interrupt_char) {
|
|
|
|
mp_sched_keyboard_interrupt();
|
|
|
|
} else {
|
|
|
|
ringbuf_put(&stdin_ringbuf, data_char);
|
|
|
|
}
|
|
|
|
} else {
|
|
|
|
cdc_itf_pending |= (1 << itf);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
2020-01-20 11:25:51 +00:00
|
|
|
|
2021-05-07 14:21:09 +01:00
|
|
|
uintptr_t mp_hal_stdio_poll(uintptr_t poll_flags) {
|
|
|
|
uintptr_t ret = 0;
|
2022-03-27 07:50:34 +01:00
|
|
|
poll_cdc_interfaces();
|
2021-07-03 17:39:17 +01:00
|
|
|
if ((poll_flags & MP_STREAM_POLL_RD) && ringbuf_peek(&stdin_ringbuf) != -1) {
|
|
|
|
ret |= MP_STREAM_POLL_RD;
|
|
|
|
}
|
2023-03-21 13:14:46 +00:00
|
|
|
if ((poll_flags & MP_STREAM_POLL_WR) && tud_cdc_connected() && tud_cdc_write_available() > 0) {
|
|
|
|
ret |= MP_STREAM_POLL_WR;
|
|
|
|
}
|
2022-03-27 07:50:34 +01:00
|
|
|
#if MICROPY_PY_OS_DUPTERM
|
2022-08-18 05:47:56 +01:00
|
|
|
ret |= mp_os_dupterm_poll(poll_flags);
|
2022-03-27 07:50:34 +01:00
|
|
|
#endif
|
2021-05-07 14:21:09 +01:00
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
2020-01-20 11:25:51 +00:00
|
|
|
int mp_hal_stdin_rx_chr(void) {
|
|
|
|
for (;;) {
|
2022-03-27 07:50:34 +01:00
|
|
|
poll_cdc_interfaces();
|
2021-07-03 17:39:17 +01:00
|
|
|
int c = ringbuf_get(&stdin_ringbuf);
|
|
|
|
if (c != -1) {
|
|
|
|
return c;
|
|
|
|
}
|
2022-03-27 07:50:34 +01:00
|
|
|
#if MICROPY_PY_OS_DUPTERM
|
2022-08-18 05:47:56 +01:00
|
|
|
int dupterm_c = mp_os_dupterm_rx_chr();
|
2022-03-27 07:50:34 +01:00
|
|
|
if (dupterm_c >= 0) {
|
|
|
|
return dupterm_c;
|
2020-01-20 11:25:51 +00:00
|
|
|
}
|
2022-03-27 07:50:34 +01:00
|
|
|
#endif
|
2021-02-12 02:32:27 +00:00
|
|
|
MICROPY_EVENT_POLL_HOOK
|
2020-01-20 11:25:51 +00:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
ports: Fix sys.stdout.buffer.write() return value.
MicroPython code may rely on the return value of sys.stdout.buffer.write()
to reflect the number of bytes actually written. While in most scenarios a
write() operation is successful, there are cases where it fails, leading to
data loss. This problem arises because, currently, write() merely returns
the number of bytes it was supposed to write, without indication of
failure.
One scenario where write() might fail, is where USB is used and the
receiving end doesn't read quickly enough to empty the receive buffer. In
that case, write() on the MicroPython side can timeout, resulting in the
loss of data without any indication, a behavior observed notably in
communication between a Pi Pico as a client and a Linux host using the ACM
driver.
A complex issue arises with mp_hal_stdout_tx_strn() when it involves
multiple outputs, such as USB, dupterm and hardware UART. The challenge is
in handling cases where writing to one output is successful, but another
fails, either fully or partially. This patch implements the following
solution:
mp_hal_stdout_tx_strn() attempts to write len bytes to all of the possible
destinations for that data, and returns the minimum successful write
length.
The implementation of this is complicated by several factors:
- multiple outputs may be enabled or disabled at compiled time
- multiple outputs may be enabled or disabled at runtime
- mp_os_dupterm_tx_strn() is one such output, optionally containing
multiple additional outputs
- each of these outputs may or may not be able to report success
- each of these outputs may or may not be able to report partial writes
As a result, there's no single strategy that fits all ports, necessitating
unique logic for each instance of mp_hal_stdout_tx_strn().
Note that addressing sys.stdout.write() is more complex due to its data
modification process ("cooked" output), and it remains unchanged in this
patch. Developers who are concerned about accurate return values from
write operations should use sys.stdout.buffer.write().
This patch might disrupt some existing code, but it's also expected to
resolve issues, considering that the peculiar return value behavior of
sys.stdout.buffer.write() is not well-documented and likely not widely
known. Therefore, it's improbable that much existing code relies on the
previous behavior.
Signed-off-by: Maarten van der Schrieck <maarten@thingsconnected.nl>
2023-06-18 10:46:25 +01:00
|
|
|
mp_uint_t mp_hal_stdout_tx_strn(const char *str, mp_uint_t len) {
|
|
|
|
mp_uint_t ret = len;
|
|
|
|
bool did_write = false;
|
2020-01-20 11:25:51 +00:00
|
|
|
if (tud_cdc_connected()) {
|
ports: Fix sys.stdout.buffer.write() return value.
MicroPython code may rely on the return value of sys.stdout.buffer.write()
to reflect the number of bytes actually written. While in most scenarios a
write() operation is successful, there are cases where it fails, leading to
data loss. This problem arises because, currently, write() merely returns
the number of bytes it was supposed to write, without indication of
failure.
One scenario where write() might fail, is where USB is used and the
receiving end doesn't read quickly enough to empty the receive buffer. In
that case, write() on the MicroPython side can timeout, resulting in the
loss of data without any indication, a behavior observed notably in
communication between a Pi Pico as a client and a Linux host using the ACM
driver.
A complex issue arises with mp_hal_stdout_tx_strn() when it involves
multiple outputs, such as USB, dupterm and hardware UART. The challenge is
in handling cases where writing to one output is successful, but another
fails, either fully or partially. This patch implements the following
solution:
mp_hal_stdout_tx_strn() attempts to write len bytes to all of the possible
destinations for that data, and returns the minimum successful write
length.
The implementation of this is complicated by several factors:
- multiple outputs may be enabled or disabled at compiled time
- multiple outputs may be enabled or disabled at runtime
- mp_os_dupterm_tx_strn() is one such output, optionally containing
multiple additional outputs
- each of these outputs may or may not be able to report success
- each of these outputs may or may not be able to report partial writes
As a result, there's no single strategy that fits all ports, necessitating
unique logic for each instance of mp_hal_stdout_tx_strn().
Note that addressing sys.stdout.write() is more complex due to its data
modification process ("cooked" output), and it remains unchanged in this
patch. Developers who are concerned about accurate return values from
write operations should use sys.stdout.buffer.write().
This patch might disrupt some existing code, but it's also expected to
resolve issues, considering that the peculiar return value behavior of
sys.stdout.buffer.write() is not well-documented and likely not widely
known. Therefore, it's improbable that much existing code relies on the
previous behavior.
Signed-off-by: Maarten van der Schrieck <maarten@thingsconnected.nl>
2023-06-18 10:46:25 +01:00
|
|
|
size_t i = 0;
|
|
|
|
while (i < len) {
|
2020-01-20 11:25:51 +00:00
|
|
|
uint32_t n = len - i;
|
2021-02-12 02:32:27 +00:00
|
|
|
if (n > CFG_TUD_CDC_EP_BUFSIZE) {
|
|
|
|
n = CFG_TUD_CDC_EP_BUFSIZE;
|
2020-01-20 11:25:51 +00:00
|
|
|
}
|
2022-10-16 11:28:05 +01:00
|
|
|
uint64_t timeout = ticks_us64() + (uint64_t)(MICROPY_HW_USB_CDC_TX_TIMEOUT * 1000);
|
|
|
|
// Wait with a max of USC_CDC_TIMEOUT ms
|
|
|
|
while (n > tud_cdc_write_available() && ticks_us64() < timeout) {
|
|
|
|
MICROPY_EVENT_POLL_HOOK
|
2021-02-12 02:32:27 +00:00
|
|
|
}
|
2022-10-16 11:28:05 +01:00
|
|
|
if (ticks_us64() >= timeout) {
|
ports: Fix sys.stdout.buffer.write() return value.
MicroPython code may rely on the return value of sys.stdout.buffer.write()
to reflect the number of bytes actually written. While in most scenarios a
write() operation is successful, there are cases where it fails, leading to
data loss. This problem arises because, currently, write() merely returns
the number of bytes it was supposed to write, without indication of
failure.
One scenario where write() might fail, is where USB is used and the
receiving end doesn't read quickly enough to empty the receive buffer. In
that case, write() on the MicroPython side can timeout, resulting in the
loss of data without any indication, a behavior observed notably in
communication between a Pi Pico as a client and a Linux host using the ACM
driver.
A complex issue arises with mp_hal_stdout_tx_strn() when it involves
multiple outputs, such as USB, dupterm and hardware UART. The challenge is
in handling cases where writing to one output is successful, but another
fails, either fully or partially. This patch implements the following
solution:
mp_hal_stdout_tx_strn() attempts to write len bytes to all of the possible
destinations for that data, and returns the minimum successful write
length.
The implementation of this is complicated by several factors:
- multiple outputs may be enabled or disabled at compiled time
- multiple outputs may be enabled or disabled at runtime
- mp_os_dupterm_tx_strn() is one such output, optionally containing
multiple additional outputs
- each of these outputs may or may not be able to report success
- each of these outputs may or may not be able to report partial writes
As a result, there's no single strategy that fits all ports, necessitating
unique logic for each instance of mp_hal_stdout_tx_strn().
Note that addressing sys.stdout.write() is more complex due to its data
modification process ("cooked" output), and it remains unchanged in this
patch. Developers who are concerned about accurate return values from
write operations should use sys.stdout.buffer.write().
This patch might disrupt some existing code, but it's also expected to
resolve issues, considering that the peculiar return value behavior of
sys.stdout.buffer.write() is not well-documented and likely not widely
known. Therefore, it's improbable that much existing code relies on the
previous behavior.
Signed-off-by: Maarten van der Schrieck <maarten@thingsconnected.nl>
2023-06-18 10:46:25 +01:00
|
|
|
ret = i;
|
2022-10-16 11:28:05 +01:00
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
2021-02-12 02:32:27 +00:00
|
|
|
uint32_t n2 = tud_cdc_write(str + i, n);
|
|
|
|
tud_cdc_write_flush();
|
2020-01-20 11:25:51 +00:00
|
|
|
i += n2;
|
|
|
|
}
|
ports: Fix sys.stdout.buffer.write() return value.
MicroPython code may rely on the return value of sys.stdout.buffer.write()
to reflect the number of bytes actually written. While in most scenarios a
write() operation is successful, there are cases where it fails, leading to
data loss. This problem arises because, currently, write() merely returns
the number of bytes it was supposed to write, without indication of
failure.
One scenario where write() might fail, is where USB is used and the
receiving end doesn't read quickly enough to empty the receive buffer. In
that case, write() on the MicroPython side can timeout, resulting in the
loss of data without any indication, a behavior observed notably in
communication between a Pi Pico as a client and a Linux host using the ACM
driver.
A complex issue arises with mp_hal_stdout_tx_strn() when it involves
multiple outputs, such as USB, dupterm and hardware UART. The challenge is
in handling cases where writing to one output is successful, but another
fails, either fully or partially. This patch implements the following
solution:
mp_hal_stdout_tx_strn() attempts to write len bytes to all of the possible
destinations for that data, and returns the minimum successful write
length.
The implementation of this is complicated by several factors:
- multiple outputs may be enabled or disabled at compiled time
- multiple outputs may be enabled or disabled at runtime
- mp_os_dupterm_tx_strn() is one such output, optionally containing
multiple additional outputs
- each of these outputs may or may not be able to report success
- each of these outputs may or may not be able to report partial writes
As a result, there's no single strategy that fits all ports, necessitating
unique logic for each instance of mp_hal_stdout_tx_strn().
Note that addressing sys.stdout.write() is more complex due to its data
modification process ("cooked" output), and it remains unchanged in this
patch. Developers who are concerned about accurate return values from
write operations should use sys.stdout.buffer.write().
This patch might disrupt some existing code, but it's also expected to
resolve issues, considering that the peculiar return value behavior of
sys.stdout.buffer.write() is not well-documented and likely not widely
known. Therefore, it's improbable that much existing code relies on the
previous behavior.
Signed-off-by: Maarten van der Schrieck <maarten@thingsconnected.nl>
2023-06-18 10:46:25 +01:00
|
|
|
did_write = true;
|
|
|
|
ret = MIN(i, ret);
|
2020-01-20 11:25:51 +00:00
|
|
|
}
|
2022-03-27 07:50:34 +01:00
|
|
|
#if MICROPY_PY_OS_DUPTERM
|
ports: Fix sys.stdout.buffer.write() return value.
MicroPython code may rely on the return value of sys.stdout.buffer.write()
to reflect the number of bytes actually written. While in most scenarios a
write() operation is successful, there are cases where it fails, leading to
data loss. This problem arises because, currently, write() merely returns
the number of bytes it was supposed to write, without indication of
failure.
One scenario where write() might fail, is where USB is used and the
receiving end doesn't read quickly enough to empty the receive buffer. In
that case, write() on the MicroPython side can timeout, resulting in the
loss of data without any indication, a behavior observed notably in
communication between a Pi Pico as a client and a Linux host using the ACM
driver.
A complex issue arises with mp_hal_stdout_tx_strn() when it involves
multiple outputs, such as USB, dupterm and hardware UART. The challenge is
in handling cases where writing to one output is successful, but another
fails, either fully or partially. This patch implements the following
solution:
mp_hal_stdout_tx_strn() attempts to write len bytes to all of the possible
destinations for that data, and returns the minimum successful write
length.
The implementation of this is complicated by several factors:
- multiple outputs may be enabled or disabled at compiled time
- multiple outputs may be enabled or disabled at runtime
- mp_os_dupterm_tx_strn() is one such output, optionally containing
multiple additional outputs
- each of these outputs may or may not be able to report success
- each of these outputs may or may not be able to report partial writes
As a result, there's no single strategy that fits all ports, necessitating
unique logic for each instance of mp_hal_stdout_tx_strn().
Note that addressing sys.stdout.write() is more complex due to its data
modification process ("cooked" output), and it remains unchanged in this
patch. Developers who are concerned about accurate return values from
write operations should use sys.stdout.buffer.write().
This patch might disrupt some existing code, but it's also expected to
resolve issues, considering that the peculiar return value behavior of
sys.stdout.buffer.write() is not well-documented and likely not widely
known. Therefore, it's improbable that much existing code relies on the
previous behavior.
Signed-off-by: Maarten van der Schrieck <maarten@thingsconnected.nl>
2023-06-18 10:46:25 +01:00
|
|
|
int dupterm_res = mp_os_dupterm_tx_strn(str, len);
|
|
|
|
if (dupterm_res >= 0) {
|
|
|
|
did_write = true;
|
|
|
|
ret = MIN((mp_uint_t)dupterm_res, ret);
|
|
|
|
}
|
2022-03-27 07:50:34 +01:00
|
|
|
#endif
|
ports: Fix sys.stdout.buffer.write() return value.
MicroPython code may rely on the return value of sys.stdout.buffer.write()
to reflect the number of bytes actually written. While in most scenarios a
write() operation is successful, there are cases where it fails, leading to
data loss. This problem arises because, currently, write() merely returns
the number of bytes it was supposed to write, without indication of
failure.
One scenario where write() might fail, is where USB is used and the
receiving end doesn't read quickly enough to empty the receive buffer. In
that case, write() on the MicroPython side can timeout, resulting in the
loss of data without any indication, a behavior observed notably in
communication between a Pi Pico as a client and a Linux host using the ACM
driver.
A complex issue arises with mp_hal_stdout_tx_strn() when it involves
multiple outputs, such as USB, dupterm and hardware UART. The challenge is
in handling cases where writing to one output is successful, but another
fails, either fully or partially. This patch implements the following
solution:
mp_hal_stdout_tx_strn() attempts to write len bytes to all of the possible
destinations for that data, and returns the minimum successful write
length.
The implementation of this is complicated by several factors:
- multiple outputs may be enabled or disabled at compiled time
- multiple outputs may be enabled or disabled at runtime
- mp_os_dupterm_tx_strn() is one such output, optionally containing
multiple additional outputs
- each of these outputs may or may not be able to report success
- each of these outputs may or may not be able to report partial writes
As a result, there's no single strategy that fits all ports, necessitating
unique logic for each instance of mp_hal_stdout_tx_strn().
Note that addressing sys.stdout.write() is more complex due to its data
modification process ("cooked" output), and it remains unchanged in this
patch. Developers who are concerned about accurate return values from
write operations should use sys.stdout.buffer.write().
This patch might disrupt some existing code, but it's also expected to
resolve issues, considering that the peculiar return value behavior of
sys.stdout.buffer.write() is not well-documented and likely not widely
known. Therefore, it's improbable that much existing code relies on the
previous behavior.
Signed-off-by: Maarten van der Schrieck <maarten@thingsconnected.nl>
2023-06-18 10:46:25 +01:00
|
|
|
return did_write ? ret : 0;
|
2020-01-20 11:25:51 +00:00
|
|
|
}
|
2021-06-13 15:42:19 +01:00
|
|
|
|
|
|
|
uint64_t mp_hal_time_ns(void) {
|
|
|
|
snvs_lp_srtc_datetime_t t;
|
|
|
|
SNVS_LP_SRTC_GetDatetime(SNVS, &t);
|
|
|
|
uint64_t s = timeutils_seconds_since_epoch(t.year, t.month, t.day, t.hour, t.minute, t.second);
|
|
|
|
return s * 1000000000ULL;
|
|
|
|
}
|
2021-07-03 17:39:17 +01:00
|
|
|
|
|
|
|
/*******************************************************************************/
|
|
|
|
// MAC address
|
|
|
|
|
2021-11-30 19:23:03 +00:00
|
|
|
void mp_hal_get_unique_id(uint8_t id[]) {
|
2021-10-20 20:24:20 +01:00
|
|
|
#if defined CPU_MIMXRT1176_cm7
|
|
|
|
*(uint32_t *)id = OCOTP->FUSEN[0x10].FUSE;
|
|
|
|
*(uint32_t *)(id + 4) = OCOTP->FUSEN[0x11].FUSE;
|
|
|
|
#else
|
2022-05-30 16:05:39 +01:00
|
|
|
*(uint32_t *)id = OCOTP->CFG0;
|
|
|
|
*(uint32_t *)(id + 4) = OCOTP->CFG1;
|
2021-10-20 20:24:20 +01:00
|
|
|
#endif
|
2021-11-30 19:23:03 +00:00
|
|
|
}
|
|
|
|
|
2021-07-03 17:39:17 +01:00
|
|
|
// Generate a random locally administered MAC address (LAA)
|
|
|
|
void mp_hal_generate_laa_mac(int idx, uint8_t buf[6]) {
|
|
|
|
// Take the MAC addr from the OTP's Configuration and Manufacturing Info
|
2021-11-30 19:23:03 +00:00
|
|
|
unsigned char id[8];
|
|
|
|
mp_hal_get_unique_id(id);
|
|
|
|
|
2022-05-30 16:05:39 +01:00
|
|
|
uint32_t *pt1 = (uint32_t *)id;
|
|
|
|
uint32_t *pt2 = (uint32_t *)(id + 4);
|
2021-11-30 19:23:03 +00:00
|
|
|
|
2021-07-03 17:39:17 +01:00
|
|
|
buf[0] = 0x02; // Locally Administered MAC
|
2022-05-30 16:05:39 +01:00
|
|
|
*(uint32_t *)&buf[1] = *pt1 ^ (*pt1 >> 8);
|
|
|
|
*(uint16_t *)&buf[4] = (uint16_t)(*pt2 ^ *pt2 >> 16);
|
2021-11-30 19:23:03 +00:00
|
|
|
buf[5] ^= (uint8_t)idx;
|
2021-07-03 17:39:17 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
// A board can override this if needed
|
|
|
|
MP_WEAK void mp_hal_get_mac(int idx, uint8_t buf[6]) {
|
|
|
|
mp_hal_generate_laa_mac(idx, buf);
|
|
|
|
}
|
|
|
|
|
|
|
|
void mp_hal_get_mac_ascii(int idx, size_t chr_off, size_t chr_len, char *dest) {
|
|
|
|
static const char hexchr[16] = "0123456789ABCDEF";
|
|
|
|
uint8_t mac[6];
|
|
|
|
mp_hal_get_mac(idx, mac);
|
|
|
|
for (; chr_len; ++chr_off, --chr_len) {
|
|
|
|
*dest++ = hexchr[mac[chr_off >> 1] >> (4 * (1 - (chr_off & 1))) & 0xf];
|
|
|
|
}
|
|
|
|
}
|