Dear Florian,

I use the following settings when using Lauterbach on the TX1 (otherwise
the watchdog reboots the machine after blocking):

echo 0 > /sys/devices/system/cpu/cpuquiet/tegra_cpuquiet/enable
echo 1 > /sys/kernel/debug/cpuidle_t210/fast_cluster_states_enable
echo 1 > /sys/kernel/debug/cpuidle_t210/slow_cluster_states_enable
echo 1 > /sys/kernel/debug/clock/csite/state
echo 0 > /proc/sys/kernel/nmi_watchdog
echo 0 > /proc/sys/kernel/watchdog_thresh
echo 0 > /proc/sys/kernel/watchdog

Hope it helps.

Best regards,

             Claudio

2017-08-24 15:24 GMT+02:00 'florian' via Jailhouse <
[email protected]>:

> Am Donnerstag, 24. August 2017 15:20:15 UTC+2 schrieb Ralf Ramsauer:
> > On 08/24/2017 03:16 PM, 'florian' via Jailhouse wrote:
> > > Am Donnerstag, 24. August 2017 15:10:05 UTC+2 schrieb Ralf Ramsauer:
> > >> On 08/24/2017 03:03 PM, 'florian' via Jailhouse wrote:
> > >>> Am Donnerstag, 24. August 2017 14:59:55 UTC+2 schrieb Henning Schild:
> > >>>> Am Thu, 24 Aug 2017 05:47:38 -0700
> > >>>> schrieb 'florian' via Jailhouse <[email protected]>:
> > >>>>
> > >>>>> I want to debug Jailhouse with a Lauterbach but getting crazy to
> load
> > >>>>> symbols into trace32. Is there any way to get an elf file as an
> > >>>>> output of the compilation process (important part for me: debug
> > >>>>> symbols of jailhouse.bin and of the inmates examples)?
> > >>>>
> > >>>> There are elf files with symbols and locations i.e.
> > >>>> hypervisor/hypervisor-intel.o
> > >>>> and
> > >>>> inmates/demos/x86/*-demo-linked.o
> > >>>>
> > >>>> Not sure whether you can use them for your Lauterbach, but should be
> > >>>> close to what you need.
> > >>>>
> > >>>> Henning
> > >>>
> > >>> Ok, then I'm on the right way. Am I right when thinking when using
> ARM then hypervisor/hypervisor.o should be the right and well linked elf
> file? (starting with .elf^^)
> > >>>
> > >> Right.
> > >>
> > >> Simply follow the compilation process, hypervisor.o is the last linked
> > >> file before the flat binary is objcopied:
> > >>
> > >>   CC      /root/workspace/jailhouse/hypervisor/uart.o
> > >>   CC      /root/workspace/jailhouse/hypervisor/uart-8250.o
> > >>   LD      /root/workspace/jailhouse/hypervisor/hypervisor.o
> > >>   OBJCOPY /root/workspace/jailhouse/hypervisor/jailhouse.bin
> > >>
> > >> Could you keep us up-to-date if Lauterbach debugging works fine or if
> > >> there are some obstacles? I'm interested in that.
> > >>
> > >> Thanks,
> > >>   Ralf
> > >
> > > Yeah of course I will like I promised to you and also Paolo.
> > > But "works fine" will be a little bit to much I think, but debugging
> itself works in this stage (but without loaded symbols).
> > > The only problem at the moment is that the TX1 sometimes do not want
> to start again after breaking with the debugger :/.
> > >
> > So resuming from the breakpoint crashes the whole system? Does this only
> > happen in combination with a hypervisor/jailhouse or is it a
> > platform-related problem?
> >
> >   Ralf
>
> It sometimtes happen if resuming from Jailhouse. But I think is no problem
> of Jailhouse, its feels more to be a problem of the debug interface of the
> TX1. It happens totally undetermenistic after break and continue. It's also
> no watchdog issue. But it also happens if Jailhouse is not running.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jailhouse" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Claudio Scordino, Ph.D.
Project Manager - Funded research projects

Evidence Srl
Via Carducci 56
56010 S.Giuliano Terme - Pisa - Italy
Phone:  +39 050 99 11 122
Mobile: + 39 393 811 7491
Fax:   +39 050 99 10 812
http://www.evidence.eu.com

-- 
You received this message because you are subscribed to the Google Groups 
"Jailhouse" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to