<div dir="ltr">Thanks i was trying to figure out how to debug this but didnt make much progress.<div>Was trying to get waf to generate verbose information of all the calls it was doing but wasnt sure how to do this.<br><br>Also saw these warnings during the compile process. Have not had a chance to dig into them to see if the conversion from unsigned int to void * is ok.<br><br>../../../bsps/microblaze/include/../../shared/dev/clock/clockimpl.h: In function '_Clock_Initialize':<br>../../../bsps/microblaze/include/../../shared/dev/clock/clockimpl.h:235:37: warning: passing argument 1 of 'microblaze_clock_handler_install' from incompatible pointer type [-Wincompatible-pointer-types]<br> 235 | Clock_driver_support_install_isr( Clock_isr );<br> | ^~~~~~~~~<br> | |<br> | rtems_isr (*)(rtems_vector_number) {aka void (*)(unsigned int)}<br>../../../bsps/microblaze/microblaze_fpga/clock/clock.c:141:37: note: in definition of macro 'Clock_driver_support_install_isr'<br> 141 | microblaze_clock_handler_install( isr )<br> | ^~~<br>../../../bsps/microblaze/microblaze_fpga/clock/clock.c:122:71: note: expected 'rtems_interrupt_handler' {aka 'void (*)(void *)'} but argument is of type 'rtems_isr (*)(rtems_vector_number)' {aka 'void (*)(unsigned int)'}<br> 122 | static void microblaze_clock_handler_install( rtems_interrupt_handler isr )<br> |<br><br><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jul 7, 2022 at 3:09 PM Alex White <<a href="mailto:alex.white@oarcorp.com">alex.white@oarcorp.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Thu, Jul 7, 2022 at 10:31 AM Sam Price <<a href="mailto:thesamprice@gmail.com" target="_blank">thesamprice@gmail.com</a>> wrote:<br>
> Is it possible i have a bad python instance ?<br>
<br>
I was able to reproduce the linker problem using the latest RTEMS upstream code.<br>
<br>
It looks like it was broken by commit a0aaa394b68727d204904b59514cb0f90840ba6f from 6 days ago.<br>
<br>
I will submit a fix.<br>
<br>
Alex<br>
<br>
><br>
><br>
> --<br>
> Thank you,<br>
><br>
> Sam Price<br>
> _______________________________________________<br>
> devel mailing list<br>
> <a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a><br>
> <a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a><br>
<br>
________________________________________<br>
From: devel <<a href="mailto:devel-bounces@rtems.org" target="_blank">devel-bounces@rtems.org</a>> on behalf of Sam Price <<a href="mailto:thesamprice@gmail.com" target="_blank">thesamprice@gmail.com</a>><br>
Sent: Thursday, July 7, 2022 10:30 AM<br>
To: <a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a><br>
Subject: linkcmds.yml problems<br>
<br>
Was trying to build the latest source builder/rtems/libbsd but ran into a linker problem.<br>
<br>
You ever see this the source linker has<br>
<br>
spec/build/bsps/microblaze/microblaze_fpga/linkcmds.yml: RAM : ORIGIN = _TEXT_START_ADDR, LENGTH = ${BSP_MICROBLAZE_FPGA_RAM_LENGTH}<br>
<br>
<br>
But the generated linker file is creating<br>
<br>
RAM : ORIGIN = _TEXT_START_ADDR, LENGTH =<br>
<br>
when building rtems without populating the BSP_MICROBLAZE_FPGA_RAM_LENGTH.<br>
<br>
<br>
<br>
My config.ini has this specified as<br>
configs/config_kcu105_cpu0.ini:BSP_MICROBLAZE_FPGA_RAM_LENGTH=0x10000000<br>
<br>
Is it possible i have a bad python instance ?<br>
<br>
<br>
--<br>
Thank you,<br>
<br>
Sam Price<br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature">Thank you,<br><br>Sam Price<br>(707) 742-3726</div>