Actions
Forum Thread Details
  • State Not Answered
  • Replies 6 replies
  • Subscribers 328 subscribers
  • Views 447 views
  • Users 0 members are here
Related

Implement Custom Peripheral as a driver

Former Member

Hi,

to implement custom peripherals in bare metal is no problem, but what if one want to implement a peripheral as a driver for the embedded linux?
I'll be grateful for any help,
Gerd

Parents
  • 0

    TY for the help.
    Where did you get:
    motor_control_bdc_6wheels@40000000{
    compatible = "digster,motor-control-bdc-6wheels-1.00.a";
    reg = <0x40000000 0x1000>;
    };

    from?
    But in order to make the dtb file consistent with the pl portion i have to modify the boot file with the .bit file for the configuration, right?

  • 0 in reply to Former Member

    motor_control_bdc_6wheels is the name of my IP-block name. @40000000 is just the HEX address. Inside the {} i just tried to edit another entry to fit my block. The compatible somehow points to the driver/developer of the block, and I wrote it as "project name,driver name".
    The reg parameter is just <base address, address space>

    Regarding the bit-file/dtb-file consistency, the dts/dtb should of course be representing your current bit file (not entirely necessary but should be). So yes, the boot.bin needs to be updated with your *.bit-file.

    However, I think (not entirely sure, could check later) that the device-tree could be left as it is as long as you are providing your own driver with HARD CODED addresses and such. The device tree is only for writing generic drivers. (Someone else might say that I'm wrong about this however...) 

Reply
  • 0 in reply to Former Member

    motor_control_bdc_6wheels is the name of my IP-block name. @40000000 is just the HEX address. Inside the {} i just tried to edit another entry to fit my block. The compatible somehow points to the driver/developer of the block, and I wrote it as "project name,driver name".
    The reg parameter is just <base address, address space>

    Regarding the bit-file/dtb-file consistency, the dts/dtb should of course be representing your current bit file (not entirely necessary but should be). So yes, the boot.bin needs to be updated with your *.bit-file.

    However, I think (not entirely sure, could check later) that the device-tree could be left as it is as long as you are providing your own driver with HARD CODED addresses and such. The device tree is only for writing generic drivers. (Someone else might say that I'm wrong about this however...) 

Children
No Data