Nios® V/II Embedded Design Suite (EDS)
Support for Embedded Development Tools, Processors (SoCs and Nios® V/II processor), Embedded Development Suites (EDSs), Boot and Configuration, Operating Systems, C and C++
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
12748 Discussions

dtb seems correct but device driver not functioning

Altera_Forum
Honored Contributor II
‎04-02-2015 09:27 PM
1,422 Views

THANKS IN ADVANCE. 

 

I've been working with Altera Cyclone V Dev Kit GSRD 14.1. I added a custom IP" UART_FIFO_AV_0" (that we've used before) that utilizes HSMC HSM_D0 and HSM_D1. "I believe" I have generated a good .dtb file.  

 

When I # ] insmod myDriver.ko 

The probe function uses:  

 

of_match_device  

platform_get_resource (should I be using of_address_to_resource ? that fails) 

request_mem_region  

of_iomap 

 

AND THEN I can see that in: /proc/device-tree/sopc@0 directory I have my entry. 

 

BUT when I try and write out to the HPS pins I see no activity. 

 

I've been going around in circles - I must be missing something fundamental. 

 

I'm attaching my *.dts file that I use to create my .dtb 

ANY IDEAS WILL BE APPRECIATED - I"VE BEEN AT THIS FOR DAYS AND I FEEL LIKE I'M GOING NOWHERE. 

Preview file
46 KB
0 Kudos

Link Copied

0 Replies
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.