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.

Sign up for GitHub

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

Jump to bottom

Requesting to guide through enabling and using EUSART and I2C peripherals for the EFR32xG24_dk2601b Board #5

Open
srihari-bg opened this issue Mar 28, 2023 · 0 comments
Open

Requesting to guide through enabling and using EUSART and I2C peripherals for the EFR32xG24_dk2601b Board #5

srihari-bg opened this issue Mar 28, 2023 · 0 comments

Comments

@srihari-bg
Copy link

Hi,
We are working on the EFR32MG24 and are trying to port zephyr for a project, in this process we are stuck with tweaking the device tree to get both EUSART peripherals and I2C0 peripheral working , We are aware that the official support for this development board is still under progress and are referring to the efr32mg24-initial-support branch for our project requirements.

I request you to clarify some of my doubts mentioned below:

  1. What files are we supposed to look into, to enable additional peripherals, is it enough to tweak device tree files?
  2. Refering to the below screenshot of the file efr32mg24.dtsi file, what are the numbers assigned to interrupts? and what is peripheral-id?
    image
  3. What exactly are GECKO_LOC and GECKO_PSEL doing with the parameters passed in the efr32mg24-pinctrl.dtsi file ?
    image

My apologies if this is not the right place for a query, I am very much new to ZephyrRTOS as well as Github and was redirected to here from a Silicon Labs forum.
It would be greatful for any help.
Thank you
SriHari BG
fkokosinski pushed a commit that referenced this issue Oct 28, 2024
@swkim101 @aescolar
Bluetooth: userchan: fix buffer overflow in hci_packet_complete()
88de271 
hci_packet_complete(buf, buf_size) should check whether buf_size is
enough.
For instance, hci_packet_complete can receive buf with buf_size 1,
leading to the buffer overflow in cmd->param_len, which is buf[3].
This can happen when rx_thread() receives two frames in 512 bytes
and the first frame size is 511. Then, rx_thread() will call
hci_packet_complete() with 1.

==5==ERROR: AddressSanitizer: global-buffer-overflow on address
0x000000ad81c2 at pc 0x0000005279b3 bp 0x7fffe74f5b70 sp 0x7fffe74f5b68

READ of size 2 at 0x000000ad81c2 thread T6
    #0 0x5279b2  (/root/zephyr.exe+0x5279b2)
    #1 0x4d697d  (/root/zephyr.exe+0x4d697d)
    #2 0x7ffff60e5daa  (/lib/x86_64-linux-gnu/libc.so.6+0x89daa)
(BuildId: 2e01923fea4ad9f7fa50fe24e0f3385a45a6cd1c)

0x000000ad81c2 is located 2 bytes to the right of global variable
'rx_thread.frame' defined in 'zephyr/drivers/bluetooth/hci/userchan.c'
(0xad7fc0) of size 512
SUMMARY: AddressSanitizer: global-buffer-overflow
(/root/zephyr.exe+0x5279b2)
Thread T6 created by T2 here:
    #0 0x48c17c  (/root/zephyr.exe+0x48c17c)
    #1 0x530192  (/root/zephyr.exe+0x530192)
    #2 0x4dcc22  (/root/zephyr.exe+0x4dcc22)

Thread T2 created by T1 here:
    #0 0x48c17c  (/root/zephyr.exe+0x48c17c)
    #1 0x530192  (/root/zephyr.exe+0x530192)
    #2 0x4dcc22  (/root/zephyr.exe+0x4dcc22)

Thread T1 created by T0 here:
    #0 0x48c17c  (/root/zephyr.exe+0x48c17c)
    #1 0x52f36c  (/root/zephyr.exe+0x52f36c)
    #2 0x5371dc  (/root/zephyr.exe+0x5371dc)
    #3 0x5312a6  (/root/zephyr.exe+0x5312a6)
    #4 0x52ed7b  (/root/zephyr.exe+0x52ed7b)
    #5 0x52eddd  (/root/zephyr.exe+0x52eddd)
    zephyrproject-rtos#6 0x7ffff6083c89  (/lib/x86_64-linux-gnu/libc.so.6+0x27c89)
(BuildId: 2e01923fea4ad9f7fa50fe24e0f3385a45a6cd1c)

==5==ABORTING

Signed-off-by: Sungwoo Kim <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@srihari-bg