Thanks, Michael I have kernel 4.1.18 + xenomai 3.0.6 works too, but can't work with ti's drm drivers. Ti's sdk[1] with own kernel based on 4.1.18, can not work with ipipe patch, and i it's hard to solve the conflict.
Now, Ti's drm driver code is in the new kernel 4.14, so the best way is that ipipe-arm can work with the 4.14 kernel. [1]. http://processors.wiki.ti.com/index.php?title=Processor_SDK_Linux_Release_Notes&oldid=214754 At 2019-01-26 17:36:34, "Michael Nazzareno Trimarchi" <[email protected]> wrote: >Hi Jack > > >On Sat, Jan 26, 2019 at 10:20 AM JackZhang via Xenomai ><[email protected]> wrote: >> >> Hi, Grep, thanks. >> >> >> >> >Have you tried this with the 4.9 or 4.4 kernel and ipipe patch? I >> >think 4.4 (which is based on a SLTS) has been tested on beaglebone >> >(similar processor). Did you mean kernel 4.14 not 3.14? >> >> I mean kernel 4.14. Sorry for mistake. >> >I think I've reproduced this on a Beaglebone which is based on a >> >similar processor, I'll look into it this week. >> Thank you very much! > >I have 4.1.6 + xenomai 3.0.7 and seems that it works > >Michael > >> >> >> 在 2019-01-22 23:18:03，"Greg Gallagher" <[email protected]> 写道： >> >On Tue, Jan 22, 2019 at 5:34 AM 张建昆 via Xenomai <[email protected]> wrote: >> >> >> >> Hello everyone, here is some new clues: >> >> 1. I tried xenomai 3.0.8, kernel 3.14.17 and >> >> ipipe-core-4.14.71-arm-4.patch. Still the same question. >> > >> >Have you tried this with the 4.9 or 4.4 kernel and ipipe patch? I >> >think 4.4 (which is based on a SLTS) has been tested on beaglebone >> >(similar processor). Did you mean kernel 4.14 not 3.14? >> > >> >> 2. It seems the system is locked up once a gpio interrupt is triggered. >> >> >> >> 3. Some debug information show that, once a gpio interrupt is triggered, >> >> the function >> >> >> >> 'omap_gpio_irq_handler' is triggered all the time. >> >I think I've reproduced this on a Beaglebone which is based on a >> >similar processor, I'll look into it this week. >> > >> >> There may be a little bug exists, but i don't know how to amend it. Thank >> >> you very much, if anyone can help. >> >> >> > >> >-Greg >> >> >------------------------------ >> >> > >> >> >Message: 3 >> >> >Date: Fri, 18 Jan 2019 11:48:12 +0800 (CST) >> >> >From: 张建昆 <[email protected]> >> >> >To: [email protected] >> >> >Subject: Help: System freeze when edge interrupt trigger, >> >> > Xenomain3.0.8, ipipe-arm main line, am335x >> >> >Message-ID: <[email protected]> >> >> >Content-Type: text/plain; charset="gbk" >> >> > >> >> >Hello! >> >> > The system freeze when interrupt is triggered. I clone ipipe-arm >> >> > master, and use xenomai 3.0.8 following xenomai startup tutorial. >> >> >The hardware cpu is am3358. System works fine after start up, but the >> >> >system immediately locks up when a edge interrupt. For example, >> >> >the mmc card in pluged in. Is it something worng ? Thank you very much! >> >> > >> >> > The kernel config file and dts attached. >> >> > >> >> > >> >> >-------------- next part -------------- >> >> >A non-text attachment was scrubbed... >> >> >Name: .config >> >> >Type: application/octet-stream >> >> >Size: 129591 bytes >> >> >Desc: not available >> >> >URL: >> >> ><http://xenomai.org/pipermail/xenomai/attachments/20190118/538175f9/attachment.obj> >> >> >-------------- next part -------------- >> >> >A non-text attachment was scrubbed... >> >> >Name: am335x-dnk-v1_LCD800x480_TM070RDH13.dts >> >> >Type: application/octet-stream >> >> >Size: 29436 bytes >> >> >Desc: not available >> >> >URL: >> >> ><http://xenomai.org/pipermail/xenomai/attachments/20190118/538175f9/attachment-0001.obj> >> >> > >> >> >------------------------------ >> >> > >> >> >Subject: Digest Footer >> >> > >> >> > >> >> > >> >> > >> >> >------------------------------ >> >> > >> >> >End of Xenomai Digest, Vol 81, Issue 17 >> >> >*************************************** > > > >-- >| Michael Nazzareno Trimarchi Amarula Solutions BV | >| COO - Founder Cruquiuskade 47 | >| +31(0)851119172 Amsterdam 1018 AM NL | >| [`as] http://www.amarulasolutions.com |
