On 30/08/2012 11:22, andy pugh wrote:
Does increasing num_bspis in the hostmot2 loading line help? I am
rather clutching at straws here.
Yes tried various permutations of different channels, num_bspis etc
There is a precompiled 2x7i65 bitfile on the Mesa site
(http://www.mesanet.com/software/parallel/5i20.zip). It might be worth
trying that to be sure it isn't a bitfile problem, but I really don't
see how it can be.
Tried this file just now; I'd built my own because I missed this.
However this firmware does not load!
->
....hm2_pci.ko': -1 unknown symbol in module
insmod failed etc
In fact the downloaded firmware is 7 bytes larger than all the other on
my system?
One thing that does puzzle me is that we are not seeing the TRAM
memory regions being allocated. But that could be the debug level
chosen.
Setting a higher level is a bit involved. You need to start realtime
with halrun, then open a second terminal and do
echo 5 > /proc/rtapi/debug
to turn on full driver debugging.
Then do the rest of the loading process, and start, and lets see if
there are any clues in that dmesg.
I've attached dmesg with debug=5. Shows pins and parameters being setup
and then breaks in the same way with no additional messages
I have forwarded the original email to Cliff.
On 30/08/2012 08:34, William Ratcliffe wrote:
No crash prior to 'start'
On 29/08/2012 23:45, andy pugh wrote:
On 29 August 2012 22:49, andy pugh <[email protected]> wrote:
It looks like *CPLD_write is an initialised pointer, and that is bad.
I am trying to comp the mesa_7i65 file to see if the c-code
initialises the pointers.
Curiously I am being told that a realtime component must include at
least one function. Which is not meant to be the case any more.
Well, that last problem was not running the rip-environment script first.
As for the segfault problem, I am a bit stumped, as the struct is
malloc-ed in the generated C and it worked for Cliff (who actually
wrote most of the .comp file)
Also, there is a surprising lack of info in the dmesg considering that
it has supposedly got as far as the "read" function.
Does it still crash without the "start" in the HAL?
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Emc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users
[ 1034.359451] HAL: creating pin 'mesa-7i65.0.analogue.1.in'
[ 1034.359457] HAL: creating pin 'mesa-7i65.0.analogue.2.in'
[ 1034.359464] HAL: creating pin 'mesa-7i65.0.analogue.3.in'
[ 1034.359471] HAL: creating pin 'mesa-7i65.0.analogue.4.in'
[ 1034.359477] HAL: creating pin 'mesa-7i65.0.analogue.5.in'
[ 1034.359484] HAL: creating pin 'mesa-7i65.0.analogue.6.in'
[ 1034.359491] HAL: creating pin 'mesa-7i65.0.analogue.7.in'
[ 1034.359499] HAL: creating pin 'mesa-7i65.0.digital.0.in'
[ 1034.359506] HAL: creating pin 'mesa-7i65.0.digital.1.in'
[ 1034.359513] HAL: creating pin 'mesa-7i65.0.digital.2.in'
[ 1034.359520] HAL: creating pin 'mesa-7i65.0.digital.3.in'
[ 1034.359527] HAL: creating pin 'mesa-7i65.0.enable.0.out'
[ 1034.359534] HAL: creating pin 'mesa-7i65.0.enable.1.out'
[ 1034.359541] HAL: creating pin 'mesa-7i65.0.enable.2.out'
[ 1034.359548] HAL: creating pin 'mesa-7i65.0.enable.3.out'
[ 1034.359555] HAL: creating pin 'mesa-7i65.0.enable.4.out'
[ 1034.359563] HAL: creating pin 'mesa-7i65.0.enable.5.out'
[ 1034.359570] HAL: creating pin 'mesa-7i65.0.enable.6.out'
[ 1034.359578] HAL: creating pin 'mesa-7i65.0.enable.7.out'
[ 1034.359585] HAL: creating pin 'mesa-7i65.0.watchdog.has-bit'
[ 1034.359593] HAL: creating parameter 'mesa-7i65.0.scale-0'
[ 1034.359602] HAL: creating parameter 'mesa-7i65.0.scale-1'
[ 1034.359608] HAL: creating parameter 'mesa-7i65.0.scale-2'
[ 1034.359614] HAL: creating parameter 'mesa-7i65.0.scale-3'
[ 1034.359620] HAL: creating parameter 'mesa-7i65.0.scale-4'
[ 1034.359626] HAL: creating parameter 'mesa-7i65.0.scale-5'
[ 1034.359632] HAL: creating parameter 'mesa-7i65.0.scale-6'
[ 1034.359639] HAL: creating parameter 'mesa-7i65.0.scale-7'
[ 1034.359645] HAL: creating parameter 'mesa-7i65.0.is-bipolar-0'
[ 1034.359652] HAL: creating parameter 'mesa-7i65.0.is-bipolar-1'
[ 1034.359658] HAL: creating parameter 'mesa-7i65.0.is-bipolar-2'
[ 1034.359666] HAL: creating parameter 'mesa-7i65.0.is-bipolar-3'
[ 1034.359673] HAL: creating parameter 'mesa-7i65.0.is-bipolar-4'
[ 1034.359680] HAL: creating parameter 'mesa-7i65.0.is-bipolar-5'
[ 1034.359687] HAL: creating parameter 'mesa-7i65.0.is-bipolar-6'
[ 1034.359693] HAL: creating parameter 'mesa-7i65.0.is-bipolar-7'
[ 1039.355521] HAL: initializing component 'threads'
[ 1039.355527] RTAPI: initing module HAL_threads
[ 1039.355531] RTAPI: module 'HAL_threads' loaded, ID: 7
[ 1039.355537] HAL: component 'threads' initialized, ID = 07
[ 1039.355540] HAL: creating thread test, 10000000 nsec
[ 1039.359578] RTAPI: clock_set_period requested: 10000000 actual: 9999903
counts requested: 124595 actual: 124594
[ 1039.360224] RTAPI: task 01 installed by module 01, priority 1, code: fc09166d
[ 1039.360232] RTAPI: start_task id: 01
[ 1039.360235] RTAPI: period_nsec: 9999903
[ 1039.360238] RTAPI: count: 124594
[ 1039.360240] HAL: thread created
[ 1039.360243] THREADS: created 10000 uS thread
[ 1067.262767] RTAPI: Task 1[f0a1b000]: Fault with vec=14, signo=11 ip=fc2f4017.
[ 1067.262771] RTAPI: This fault may not be recoverable without rebooting.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Emc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users
