[mkleox]

When we connect a keyboard, USB flash, or a camera instead of the BRK-B board to the USB connector of the BRK-A board, it works, however, it seems that the RNDIS-host driver is not loaded on the BRK-A board, that’s why when we connect the BRK-B to BRK-A, it doesn’t recognize the board.

[mkleox]

Hi Coloradocarlos,

Thanks for helping us with this issue.

Here is the schematic of the connected hardware:

 

 

Attachments:

1. 

   Connection.jpg
   

[mkleox]

Hi,
We also would like to show our deep interest in such a document. This would be really a game-changing document.
I personally am working on modifying the Debian Image, device tree, and the config files from the provided image. it takes months to figure out what to change… there are not really simple steps showing what to do first, we somehow are reverse-engineering the build process to modify something!

We appreciate the help from octavo.

[mkleox]

Dear Octavo, we also appreciate the help on this issue.

Overall a minimum Debian Build Step with a minimum dtb would be a great option here.

Tnx

[mkleox]

Dear Neeraj,

Thank you so much for the reply. This was really helpful.

Just one more request; Is there any CubeMX project for the brk board that you can share with us?

I used the OSD32MP15x_MinimalConfig.zip provided here: https://octavosystems.com/app_notes/stm32mp1-cubemx-tutorial-for-osd32mp15x/

but after the compilation, when I replace the .dtb file in the bootfs of the Debian image with the new .dtb file from CubeMX output, the board does not boot successfully.

[mkleox]

This is also our question.

@octavo: Thanks for helping us.

[mkleox]

Thank you so much for sharing this.
I wanted to ask if there is any simple instruction for the preparation of the environment and compilation for the brk boards?

We are new to the Device Tree and the embedded Linux compilation.
We are developing our system based on this processor and this would really help us in facilitating the development of the final product.

[mkleox]

Hi,

I appreciate it if we could get a general time schedule for this announcement.

BR,
Leox

• This reply was modified 3 years, 8 months ago by mkleox.

[mkleox]

Hi,

Thank you for the prompt response.
This is great news.

looking forward to the announcement.

BR,
Leox

[mkleox]

Hi,
You can change the CPU clock in the .dtb file and reset the systemctl. Here is how:

Go to the

$cd /boot

the dst file must be there:

/boot/stm32mp157c-osd32mp157c-brk.dtb

I did not try for the BRK, but for RED it worked. But I think BRK might use a different CPU clock model. but you can try this:

$sudo fdtput -t i /boot/stm32mp157c-osd32mp157c-brk.dtb /cpus/cpu@0 clock-frequency 800000000
$sudo fdtput -t i /boot/stm32mp157c-osd32mp157c-brk.dtb /cpus/cpu@1 clock-frequency 800000000

and then restart the board or run

$sudo systemctl reboot

another way:
in case you want to see the difference between the BRK and RED dtb, you can decompile the dtb files into dts and change it and recompile it again. you can use this:

$sudo dtc -I dtb -O dts stm32mp157c-osd32mp157c-brk.dtb -o stm32mp157c-osd32mp157c-brk.dts

for that you might need to install the dtc compiler.

$sudo apt-get install device-tree-compiler

Let us know if that works also for BRK. 🙂

[Author]

Posts