2014-07-21T00:09:43 *** gigetoo has quit IRC (Ping timeout: 250 seconds) 2014-07-21T00:12:07 *** gigetoo has joined #rtems 2014-07-21T00:20:01 *** gigetoo has quit IRC (Ping timeout: 256 seconds) 2014-07-21T00:21:11 *** gigetoo has joined #rtems 2014-07-21T00:29:22 *** gigetoo has quit IRC (Ping timeout: 240 seconds) 2014-07-21T00:31:15 *** gigetoo has joined #rtems 2014-07-21T00:39:18 *** gigetoo has quit IRC (Ping timeout: 250 seconds) 2014-07-21T00:40:40 *** gigetoo has joined #rtems 2014-07-21T00:48:52 *** gigetoo has quit IRC (Ping timeout: 240 seconds) 2014-07-21T00:50:30 *** gigetoo has joined #rtems 2014-07-21T00:59:07 *** gigetoo has quit IRC (Ping timeout: 256 seconds) 2014-07-21T01:00:59 *** gigetoo has joined #rtems 2014-07-21T01:09:05 *** gigetoo has quit IRC (Ping timeout: 250 seconds) 2014-07-21T01:10:47 *** gigetoo has joined #rtems 2014-07-21T01:18:54 *** gigetoo has quit IRC (Ping timeout: 255 seconds) 2014-07-21T01:20:00 *** gigetoo has joined #rtems 2014-07-21T01:28:28 *** gigetoo has quit IRC (Ping timeout: 260 seconds) 2014-07-21T01:29:28 *** gigetoo has joined #rtems 2014-07-21T01:36:31 *** gigetoo has quit IRC (Ping timeout: 256 seconds) 2014-07-21T01:43:40 *** gigetoo has joined #rtems 2014-07-21T01:51:52 *** gigetoo has quit IRC (Ping timeout: 240 seconds) 2014-07-21T01:53:44 *** gigetoo has joined #rtems 2014-07-21T02:01:52 *** gigetoo has quit IRC (Ping timeout: 245 seconds) 2014-07-21T02:03:10 *** gigetoo has joined #rtems 2014-07-21T02:06:17 *** gigetoo has quit IRC (Read error: Connection reset by peer) 2014-07-21T02:06:49 *** zoso has joined #rtems 2014-07-21T02:08:40 *** gigetoo has joined #rtems 2014-07-21T02:18:16 *** gigetoo has quit IRC (Read error: Connection reset by peer) 2014-07-21T02:18:49 *** gigetoo has joined #rtems 2014-07-21T02:25:54 *** gigetoo has quit IRC (Ping timeout: 250 seconds) 2014-07-21T02:27:43 *** gigetoo has joined #rtems 2014-07-21T02:34:52 *** gigetoo has quit IRC (Ping timeout: 245 seconds) 2014-07-21T02:36:18 *** gigetoo has joined #rtems 2014-07-21T02:43:32 *** gigetoo has quit IRC (Ping timeout: 245 seconds) 2014-07-21T02:44:53 *** gigetoo has joined #rtems 2014-07-21T02:53:22 *** gigetoo has quit IRC (Ping timeout: 240 seconds) 2014-07-21T02:54:50 *** gigetoo has joined #rtems 2014-07-21T03:02:24 *** kiwichris has quit IRC () 2014-07-21T03:03:08 *** edwardk has quit IRC (Quit: Computer has gone to sleep.) 2014-07-21T03:04:05 *** gigetoo has quit IRC (Read error: Connection reset by peer) 2014-07-21T03:04:38 *** gigetoo has joined #rtems 2014-07-21T03:07:50 *** edwardk has joined #rtems 2014-07-21T03:12:04 *** gigetoo has quit IRC (Ping timeout: 260 seconds) 2014-07-21T03:14:31 *** gigetoo has joined #rtems 2014-07-21T03:22:26 *** kiwichris has joined #rtems 2014-07-21T03:23:32 *** gigetoo has quit IRC (Ping timeout: 250 seconds) 2014-07-21T03:25:10 *** gigetoo has joined #rtems 2014-07-21T03:33:22 *** gigetoo has quit IRC (Read error: Connection reset by peer) 2014-07-21T03:33:56 *** gigetoo has joined #rtems 2014-07-21T03:41:02 *** gigetoo has quit IRC (Ping timeout: 245 seconds) 2014-07-21T03:43:58 *** gigetoo has joined #rtems 2014-07-21T03:52:22 *** gigetoo has quit IRC (Ping timeout: 245 seconds) 2014-07-21T03:55:01 *** gigetoo has joined #rtems 2014-07-21T04:03:01 *** gigetoo has quit IRC (Read error: Connection reset by peer) 2014-07-21T04:03:35 *** gigetoo has joined #rtems 2014-07-21T04:10:42 *** gigetoo has quit IRC (Ping timeout: 240 seconds) 2014-07-21T04:13:26 *** gigetoo has joined #rtems 2014-07-21T04:22:17 *** gigetoo has quit IRC (Ping timeout: 245 seconds) 2014-07-21T04:24:39 *** gigetoo has joined #rtems 2014-07-21T04:33:16 *** gigetoo has quit IRC (Read error: Connection reset by peer) 2014-07-21T04:33:54 *** gigetoo has joined #rtems 2014-07-21T04:41:03 *** gigetoo has quit IRC (Ping timeout: 240 seconds) 2014-07-21T04:43:43 *** gigetoo has joined #rtems 2014-07-21T04:52:24 *** gigetoo has quit IRC (Ping timeout: 260 seconds) 2014-07-21T04:54:05 *** gigetoo has joined #rtems 2014-07-21T05:02:20 *** gigetoo has quit IRC (Ping timeout: 250 seconds) 2014-07-21T05:04:59 *** gigetoo has joined #rtems 2014-07-21T05:12:35 *** gigetoo has quit IRC (Ping timeout: 264 seconds) 2014-07-21T05:14:58 *** gigetoo has joined #rtems 2014-07-21T05:24:08 *** gigetoo has quit IRC (Ping timeout: 255 seconds) 2014-07-21T05:26:04 *** gigetoo has joined #rtems 2014-07-21T05:34:29 *** edwardk has quit IRC (Quit: Computer has gone to sleep.) 2014-07-21T05:34:52 *** gigetoo has quit IRC (Ping timeout: 240 seconds) 2014-07-21T05:36:04 *** gigetoo has joined #rtems 2014-07-21T05:43:35 *** gigetoo has quit IRC (Ping timeout: 256 seconds) 2014-07-21T05:44:38 *** gigetoo has joined #rtems 2014-07-21T05:55:11 *** gigetoo has quit IRC (Ping timeout: 264 seconds) 2014-07-21T05:58:09 *** gigetoo has joined #rtems 2014-07-21T06:05:59 *** gigetoo has quit IRC (Ping timeout: 264 seconds) 2014-07-21T06:08:21 *** gigetoo has joined #rtems 2014-07-21T06:11:31 *** zoso has quit IRC (Read error: Connection reset by peer) 2014-07-21T06:16:29 *** gigetoo has quit IRC (Read error: Connection reset by peer) 2014-07-21T06:17:06 *** gigetoo has joined #rtems 2014-07-21T06:24:27 *** gigetoo has quit IRC (Ping timeout: 255 seconds) 2014-07-21T06:25:42 *** gigetoo has joined #rtems 2014-07-21T06:32:49 *** zoso has joined #rtems 2014-07-21T06:33:35 *** gigetoo has quit IRC (Read error: Connection reset by peer) 2014-07-21T06:34:10 *** gigetoo has joined #rtems 2014-07-21T06:35:26 *** monstr has joined #rtems 2014-07-21T06:41:27 *** gigetoo has quit IRC (Ping timeout: 250 seconds) 2014-07-21T06:42:45 *** gigetoo has joined #rtems 2014-07-21T06:50:27 *** gigetoo has quit IRC (Ping timeout: 256 seconds) 2014-07-21T06:52:32 *** gigetoo has joined #rtems 2014-07-21T06:59:39 *** gigetoo has quit IRC (Ping timeout: 250 seconds) 2014-07-21T07:01:06 *** gigetoo has joined #rtems 2014-07-21T07:08:32 *** gigetoo has quit IRC (Ping timeout: 245 seconds) 2014-07-21T07:09:49 *** gigetoo has joined #rtems 2014-07-21T07:19:12 *** gigetoo has quit IRC (Ping timeout: 240 seconds) 2014-07-21T07:19:51 *** gigetoo has joined #rtems 2014-07-21T07:27:51 *** gigetoo has quit IRC (Ping timeout: 256 seconds) 2014-07-21T07:29:25 *** gigetoo has joined #rtems 2014-07-21T07:38:57 *** gigetoo has quit IRC (Ping timeout: 245 seconds) 2014-07-21T07:40:14 *** gigetoo has joined #rtems 2014-07-21T07:41:42 *** monstr has quit IRC (Ping timeout: 240 seconds) 2014-07-21T07:47:33 *** gigetoo has quit IRC (Ping timeout: 240 seconds) 2014-07-21T07:49:27 *** gigetoo has joined #rtems 2014-07-21T07:57:35 *** gigetoo has quit IRC (Ping timeout: 264 seconds) 2014-07-21T07:58:19 *** gigetoo has joined #rtems 2014-07-21T08:00:53 *** gigetoo has joined #rtems 2014-07-21T08:05:02 *** stryx` has joined #rtems 2014-07-21T08:08:42 *** gigetoo has quit IRC (Ping timeout: 240 seconds) 2014-07-21T08:10:21 *** gigetoo has joined #rtems 2014-07-21T08:19:08 *** gigetoo has quit IRC (Ping timeout: 260 seconds) 2014-07-21T08:21:29 *** gigetoo has joined #rtems 2014-07-21T08:29:37 *** gigetoo has quit IRC (Ping timeout: 256 seconds) 2014-07-21T08:31:31 *** gigetoo has joined #rtems 2014-07-21T08:39:45 *** gigetoo has quit IRC (Ping timeout: 250 seconds) 2014-07-21T08:41:50 *** gigetoo has joined #rtems 2014-07-21T08:43:46 *** monstr has joined #rtems 2014-07-21T08:49:12 *** gigetoo has quit IRC (Ping timeout: 240 seconds) 2014-07-21T08:51:35 *** gigetoo has joined #rtems 2014-07-21T08:57:05 *** gigetoo has quit IRC (Read error: Connection reset by peer) 2014-07-21T08:58:39 *** gigetoo has joined #rtems 2014-07-21T09:01:11 *** zoso has quit IRC (Quit: Leaving) 2014-07-21T09:08:12 *** gigetoo has quit IRC (Ping timeout: 245 seconds) 2014-07-21T09:10:32 *** gigetoo has joined #rtems 2014-07-21T09:17:52 *** gigetoo has quit IRC (Ping timeout: 240 seconds) 2014-07-21T09:20:17 *** gigetoo has joined #rtems 2014-07-21T09:27:44 *** gigetoo has quit IRC (Ping timeout: 260 seconds) 2014-07-21T09:29:58 *** gigetoo has joined #rtems 2014-07-21T09:38:57 *** gigetoo has quit IRC (Ping timeout: 245 seconds) 2014-07-21T09:41:10 *** gigetoo has joined #rtems 2014-07-21T09:50:05 *** gigetoo has quit IRC (Ping timeout: 256 seconds) 2014-07-21T09:51:16 *** gigetoo has joined #rtems 2014-07-21T09:58:22 *** gigetoo has quit IRC (Ping timeout: 240 seconds) 2014-07-21T09:59:16 *** edwardk has joined #rtems 2014-07-21T10:00:56 *** gigetoo has joined #rtems 2014-07-21T10:08:47 *** gigetoo has quit IRC (Ping timeout: 256 seconds) 2014-07-21T10:09:48 *** gigetoo has joined #rtems 2014-07-21T10:17:22 *** gigetoo has quit IRC (Ping timeout: 240 seconds) 2014-07-21T10:19:38 *** gigetoo has joined #rtems 2014-07-21T10:26:57 *** gigetoo has quit IRC (Ping timeout: 245 seconds) 2014-07-21T10:27:56 *** gigetoo has joined #rtems 2014-07-21T10:35:52 *** gigetoo has quit IRC (Ping timeout: 240 seconds) 2014-07-21T10:37:22 *** gigetoo has joined #rtems 2014-07-21T10:45:17 *** gigetoo has quit IRC (Ping timeout: 245 seconds) 2014-07-21T10:47:30 *** gigetoo has joined #rtems 2014-07-21T10:55:13 *** gigetoo has quit IRC (Ping timeout: 240 seconds) 2014-07-21T10:57:42 *** gigetoo has joined #rtems 2014-07-21T11:06:57 *** gigetoo has quit IRC (Ping timeout: 245 seconds) 2014-07-21T11:09:02 *** gigetoo has joined #rtems 2014-07-21T11:11:33 *** monstr has quit IRC (Remote host closed the connection) 2014-07-21T11:14:22 *** gigetoo has quit IRC (Ping timeout: 240 seconds) 2014-07-21T11:18:04 *** gigetoo has joined #rtems 2014-07-21T11:26:57 *** gigetoo has quit IRC (Ping timeout: 245 seconds) 2014-07-21T11:29:23 *** gigetoo has joined #rtems 2014-07-21T11:34:56 *** gigetoo has quit IRC (Ping timeout: 250 seconds) 2014-07-21T11:41:28 *** gigetoo has joined #rtems 2014-07-21T11:42:32 *** warptrosse has joined #rtems 2014-07-21T11:50:23 *** gigetoo has quit IRC (Ping timeout: 264 seconds) 2014-07-21T11:51:06 *** gigetoo has joined #rtems 2014-07-21T11:59:51 *** gigetoo has quit IRC (Ping timeout: 256 seconds) 2014-07-21T12:02:06 *** gigetoo has joined #rtems 2014-07-21T12:02:48 *** gigetoo has quit IRC (Read error: Connection reset by peer) 2014-07-21T15:05:37 *** warptrosse has quit IRC (Quit: Page closed) 2014-07-21T16:47:11 *** edwardk has quit IRC (Quit: Computer has gone to sleep.) 2014-07-21T16:56:24 *** kiwichris has quit IRC () 2014-07-21T16:56:56 *** kiwichris has joined #rtems 2014-07-21T17:09:09 *** kiwichris has quit IRC () 2014-07-21T18:04:05 *** kiwichris has joined #rtems 2014-07-21T18:30:11 *** edwardk has joined #rtems 2014-07-21T18:34:54 *** edwardk has quit IRC (Read error: Connection reset by peer) 2014-07-21T18:35:10 *** edwardk has joined #rtems 2014-07-21T18:57:46 *** atgreen has joined #rtems 2014-07-21T19:03:47 *** edwardk has quit IRC (Quit: Computer has gone to sleep.) 2014-07-21T20:31:45 *** edwardk has joined #rtems 2014-07-21T20:36:44 *** edwardk has quit IRC (Quit: Computer has gone to sleep.) 2014-07-21T21:25:49 *** edwardk has joined #rtems 2014-07-21T21:27:17 *** edwardk has quit IRC (Client Quit) 2014-07-21T21:52:58 *** kiwichris has quit IRC (Read error: Connection reset by peer) 2014-07-21T21:58:48 *** kiwichris has joined #rtems 2014-07-21T23:50:07 *** monstr has joined #rtems 2014-07-22T02:11:33 *** kiwichris has quit IRC (Read error: Connection reset by peer) 2014-07-22T03:11:33 *** zoso has joined #rtems 2014-07-22T03:40:37 *** kiwichris has joined #rtems 2014-07-22T04:14:07 *** peerst has quit IRC (Quit: peerst) 2014-07-22T04:29:10 *** peerst has joined #rtems 2014-07-22T04:33:18 *** zoso has quit IRC (Ping timeout: 255 seconds) 2014-07-22T04:47:56 *** zoso has joined #rtems 2014-07-22T04:54:48 *** ysionneau has quit IRC (*.net *.split) 2014-07-22T04:55:00 *** ysionneau has joined #rtems 2014-07-22T05:03:12 *** edwardk has joined #rtems 2014-07-22T06:31:55 *** AoLaD has joined #rtems 2014-07-22T06:55:55 *** ppisa has joined #rtems 2014-07-22T06:59:24 *** freenix has joined #rtems 2014-07-22T07:15:12 *** Hesham has joined #rtems 2014-07-22T07:20:15 *** atgreen has quit IRC (Ping timeout: 255 seconds) 2014-07-22T07:28:18 Hi kiwichris, do you have some time for questions before the meeting? 2014-07-22T07:29:39 *** AoLaD has joined #rtems 2014-07-22T07:41:25 *** asuolen has joined #rtems 2014-07-22T07:51:43 *** JustJanek has joined #rtems 2014-07-22T07:55:28 *** phipse has joined #rtems 2014-07-22T07:55:38 hi 2014-07-22T07:57:16 hi 2014-07-22T07:57:55 *** gedare has joined #rtems 2014-07-22T07:57:55 *** ChanServ sets mode: +o gedare 2014-07-22T07:58:29 *** Sched has joined #rtems 2014-07-22T07:59:13 Good morning 2014-07-22T07:59:34 Good morning 2014-07-22T07:59:36 *** jenniferA has joined #rtems 2014-07-22T07:59:40 Hi 2014-07-22T08:00:02 https://docs.google.com/document/d/1YCyUeBTsep0qYsqqN6vSWZfZdRBvVcCK35Wjv-oN9NM/edit 2014-07-22T08:00:21 Hesham: would you like to go first? 2014-07-22T08:00:27 here 2014-07-22T08:00:42 Hesham: kiwichris isn't here 2014-07-22T08:00:45 gedare: I would like to be the last one to discuss some problems with my project 2014-07-22T08:00:56 ok well I'm not sure what we'll be able to resolve, but sure. 2014-07-22T08:01:15 AoLaD: will you like to go? hi ppisa 2014-07-22T08:02:16 Hello Gedare, I am back from Corsica. AoLaD go on. 2014-07-22T08:03:12 Hi gedare 2014-07-22T08:03:30 After last week I have some basic irq and clock driver. It is definitely not finite. I will rewrite it atleast two times more. But this is compilable and testable. It is finaly on github 2014-07-22T08:03:52 AoLaD: the error you send me is that you have C code inside of an assembly .S file. You can't declare C types in assembly. 2014-07-22T08:04:11 well, the assembly file start.S is including status.h 2014-07-22T08:04:27 there needs to be some better guards about this include. 2014-07-22T08:04:39 well the thing is that the error remain even I erase the code 2014-07-22T08:04:45 hmm. ok 2014-07-22T08:04:52 And I was quite sure that it is on right place 2014-07-22T08:05:35 but probably I am wrong. I am just glad that I dont have it now 2014-07-22T08:06:02 I will be present on university tomorrow, so I can look at problem in person. 2014-07-22T08:06:15 ok good 2014-07-22T08:07:00 all right, so this week you'll be working to test, clean up, and improve the code? 2014-07-22T08:07:01 So for the next week. I'll be more testing and debuging the drivers 2014-07-22T08:07:32 yes 2014-07-22T08:07:58 ok, and you will work on the better solution to irq handling with ppisa ? 2014-07-22T08:08:25 Its on the scheduce tomorow 2014-07-22T08:08:44 thanks. anything else? 2014-07-22T08:08:57 asuolen: would you like to go next? 2014-07-22T08:09:05 sure 2014-07-22T08:09:41 *** freenix has quit IRC (Ping timeout: 256 seconds) 2014-07-22T08:10:40 ok go ahead asuolen 2014-07-22T08:10:48 so, for this week I have been working on the SPI bus, providing the low level functions to access the bus. 2014-07-22T08:11:45 I am righ now testing these with a memory device, for which I am writing the driver code so I can test the bus 2014-07-22T08:12:21 ok good, and I saw that you and Alan have some devices to play with once you get the bus code debugged? 2014-07-22T08:13:21 yes. Right now the bus code should be working, but I can only be sure when I have a device actually using it 2014-07-22T08:13:43 ok. is this code fairly raspberrypi-specific? 2014-07-22T08:13:51 the bus code? 2014-07-22T08:13:54 yeah 2014-07-22T08:14:08 yes the low level functions to access the bus are 2014-07-22T08:14:11 ok 2014-07-22T08:14:30 as for the memory device driver it can reside on libchip 2014-07-22T08:14:44 RTEMS needs some better driver models so this kind of work is easier. :) 2014-07-22T08:14:53 that might be a nice contribution 2014-07-22T08:15:12 as a matter of fact, there is currently a driver on libchip for a similar device. I am basing my driver on that on to speed the develoment 2014-07-22T08:15:51 ok 2014-07-22T08:16:12 anything else? 2014-07-22T08:16:36 think you'll have the SPI working this week? 2014-07-22T08:17:29 yes, it should be done this week 2014-07-22T08:18:24 thanks 2014-07-22T08:18:37 JustJanek: can you go next? hi phipse 2014-07-22T08:18:54 yeah, no problem 2014-07-22T08:19:15 I have mainly worked on documenting this week, I have made a blog post specifying the steps taken and why they were taken to get arinc653 partition calls working on rtems. I have looked a bit onto including header files to the project for the arinc653 functions, I only don't know how to get an additional folder created in the include directory for rtems build, which by the way, I am currently simply including POK's arinc653 header f 2014-07-22T08:19:15 iles which I'm not sure if that's the proper way to go (licensing?). 2014-07-22T08:19:17 hi 2014-07-22T08:20:18 including headers is usually fine, and I think POK is nicely licensed. 2014-07-22T08:20:36 well, i need it to reside 2014-07-22T08:20:40 in a specific folder 2014-07-22T08:20:51 so include/arinc653/ 2014-07-22T08:21:22 since the source files includes arinc653/
2014-07-22T08:22:03 so all references to the arinc653 header files assumes that there's an arinc653 directory in the include folder 2014-07-22T08:22:29 ok.. the way to do it is to define in some Makefile.am an include_HEADERS=include/arinc653 2014-07-22T08:22:43 so if you do something like... 2014-07-22T08:22:52 add cpukit/arinc653/ 2014-07-22T08:23:03 then in cpukit/arinc653/Makefile.am you would have the line 2014-07-22T08:23:08 include_HEADERS=include/arinc653 2014-07-22T08:23:17 see for example cpukit/rtems/ 2014-07-22T08:24:12 hmm, and to include a specific header file into the arinc653 folder do i need something else specifiek in the makefile? 2014-07-22T08:25:48 yeah you will setup some include_arinc653dir = $(includedir)/arinc653 2014-07-22T08:25:51 and then do 2014-07-22T08:25:59 include_arinc653_HEADERS = ....... 2014-07-22T08:26:22 all of the headers you want to put into the arinc653dir should get assigned into the include_arinc653_HEADERS variable. 2014-07-22T08:26:52 please please please when you get stuck on something like this, ask on the mailing list or at least send an email to your mentors. 2014-07-22T08:27:38 oh sorry, I just bypassed that step for now by simply copy-pasting it but automating it just seemed the nicer solution to this 2014-07-22T08:28:19 what is your plan for next week? 2014-07-22T08:28:36 ok, just don't get stuck on something. 2014-07-22T08:28:40 without asking for help ;0 2014-07-22T08:29:29 I want to try what's mentioned before on including header files. but what I also want to focus on is trying other arinc653 calls and just check which ones work already and which ones need some tweaking 2014-07-22T08:29:32 and kinda go from there 2014-07-22T08:31:10 ok. If I get your blogpost correctly, you are able to make a ARINC call from inside RTEMS to POK? 2014-07-22T08:31:27 ok, you should also start to get some code examples put together. 2014-07-22T08:32:20 code examples for rtems' examples or just in general? 2014-07-22T08:34:01 um, for using ARINC calls from RTEMS to POK. 2014-07-22T08:35:05 Like the hello world sample in rtems/testsuites/samples/, showing what can already be done with arinc 2014-07-22T08:35:13 and what has to be done to get there 2014-07-22T08:36:22 so something that defines the steps somebody has to take or just examples so somebody who's got it working can try out the arinc653 calls? 2014-07-22T08:36:44 both if possible, although a readme is fine for the first part. 2014-07-22T08:37:20 okay, i'm not sure if ill get to it this week but it'll definitely be on the backlog 2014-07-22T08:37:35 ok 2014-07-22T08:37:49 thanks JustJanek. Sched would you like to go next? 2014-07-22T08:37:59 Ok 2014-07-22T08:39:43 I was trying to make the interrupt delivery code running correctly last week. I made some slightly change of interrupt storage struct in vCPU. I change the interrupt handler of pit(timer), but the pit interrupt handler isn't invoked and I'm still trying to find out reason. I draft a post about my changes but plan to upload it after the time example works. 2014-07-22T08:40:48 I planed to runing timer in testHypercall and then rtems-guest next step. 2014-07-22T08:40:55 Can you explain the problem in more detail? 2014-07-22T08:42:35 Yes, I using GDB to debug the pok, and after the initialization is done, the interrupt did not happen, and the gdb stop on forever-loop in entry.S. 2014-07-22T08:42:49 *** zoso has quit IRC (Quit: Leaving) 2014-07-22T08:43:00 I think I can figure out this problem, but need some times. 2014-07-22T08:43:30 gdb loops in entry.S of RTEMS? 2014-07-22T08:43:36 no, in pok 2014-07-22T08:43:55 it seems the pok's partitions did no running 2014-07-22T08:44:24 or the interrupt did not set correctly. 2014-07-22T08:44:36 so the pok_loader_load_partition doesn't work anymore? 2014-07-22T08:44:52 phipse, did you know what's teh begin of partition? 2014-07-22T08:45:25 phipse, did you know what's the beginning of partition? 2014-07-22T08:46:43 in the pok_boot ,pok_arch_preempt_enable() will open the interrupt, then the partition will start to run, is my hypothesis right? 2014-07-22T08:47:00 the partition is an elf binary, this binary has an specified entry point, which is returned by the elf_loader to the partition_load function and then set as the main_thread to start off the partition. 2014-07-22T08:48:46 aha...I did not know this before. So I will grab this to find what's the problem of interrupt. 2014-07-22T08:49:09 I will update a blog after the code is work. 2014-07-22T08:49:22 please don't spend too much time without making progress. ask for help, it is OK. 2014-07-22T08:50:01 pok_partition_init calls pok_loader_load_partition, which in turn calls pok_loader_elf_load, which loads the partition binary into memory and returns the entry point instruction pointer, which ends up in kernel/core/partition.c:234 as pok_partition[i].thread_main_entry 2014-07-22T08:50:33 But the bug is made by my code. And I send you a email, I want to know what's the function of pok_bsp_irq_register_hw 2014-07-22T08:51:43 please come with questions. But please provide an analysis, where you think it goes wrong, and why you think it is going wrong there. 2014-07-22T08:52:43 I notice that you set no handler in pok_arch_event_register for timer, and I trying to using the normal interrupt handler for timer. Is this practicable？ 2014-07-22T08:53:09 Sched: perhaps post your code even though it is broken, and send an email about it 2014-07-22T08:53:23 or discuss with phipse after the meeting ends? 2014-07-22T08:53:27 I have to look at the code for this, we should talk about this seperately. What are your goals for the next week? 2014-07-22T08:53:32 Ok, 2014-07-22T08:54:15 If this bug is solved, the testHypercall will work. 2014-07-22T08:54:35 then start to RTEMS interrupt handler part. 2014-07-22T08:55:19 ok, so bug tracing, please write a blog post, where you analyse the problem, so we have some notes about it for the future. 2014-07-22T08:55:33 gedare, I'm familiar with RTEMS interrupt, is there some analysis of it? 2014-07-22T08:55:41 OK. 2014-07-22T08:56:18 yeah http://rtems.org/onlinedocs/doc-current/share/rtems/html/cpu_supplement/Port-Specific-Information-Interrupt-Processing.html#Port-Specific-Information-Interrupt-Processing 2014-07-22T08:56:19 Thank you, If not, I will trace the source code myself, but it will be so difficult. 2014-07-22T08:56:28 Thank you very much 2014-07-22T08:56:48 phipse, I will 2014-07-22T08:56:52 thanks Sched. Hesham you can go now 2014-07-22T08:56:52 post blog. 2014-07-22T08:57:02 OK 2014-07-22T08:57:30 I have been working on ticker.exe and interrupt handler, context switch issues. Now _Watchdog_Remove, _Thread_Delay_ended are called the correct number of times (three times), and _ISR_Dispatch is called three times after tasks are waken up (one for each task), but still the context switch is not done properly and ticker hangs at IDLE tasks. 2014-07-22T08:58:00 I think Context Switch is not done correctly after tasks are waken up 2014-07-22T08:58:00 you got Joel's patch yesterday? 2014-07-22T08:58:13 and noted his comments? 2014-07-22T08:58:15 Which one? 2014-07-22T08:58:31 [PATCH] or1k hacks to compile again 2014-07-22T08:58:34 Aha sure 2014-07-22T08:58:45 and comments at "Problem with ticker.exe for or1ksim/OpenRISC BSP" 2014-07-22T08:58:48 And applied it, fixed the code according to his comments 2014-07-22T08:58:51 ok 2014-07-22T08:59:10 next you'll have to step through ISR_Dispatch code 2014-07-22T08:59:19 And it's compiling and the previous problems have been avoided 2014-07-22T08:59:19 and see where it is going wrong 2014-07-22T08:59:30 in ISR_Dispatch 2014-07-22T08:59:49 I am saving the context and jump to _Thread_Dispatch 2014-07-22T08:59:54 Joel asked you for some clarifications and code, please respond to his requests 2014-07-22T09:00:03 ok 2014-07-22T09:00:14 that is the right thing to do, so you just need to figure out where it goes wrong 2014-07-22T09:00:22 The code is at github, I will reply again 2014-07-22T09:00:28 I have some questions 2014-07-22T09:00:51 When the task context is stored and added to the chain? After a call to task_wake_after() ? 2014-07-22T09:00:52 sure. anyone else can go though, the meeting is adjourned 2014-07-22T09:00:58 I'll continue with Hesham for now. 2014-07-22T09:01:03 thanks everyone 2014-07-22T09:01:20 added to which chain? 2014-07-22T09:01:33 task_wake_after() adds the task to the Watchdog_Chain. 2014-07-22T09:01:34 tasks' chain 2014-07-22T09:01:59 So, when the task context is saved to be restored after been waken up? 2014-07-22T09:02:04 https://docs.google.com/document/d/1YCyUeBTsep0qYsqqN6vSWZfZdRBvVcCK35Wjv-oN9NM/edit 2014-07-22T09:02:11 yes 2014-07-22T09:02:20 there is a normal "context_save" 2014-07-22T09:02:31 Where ? 2014-07-22T09:04:07 in 2014-07-22T09:04:13 rtems/src/taskwakeafter.c 2014-07-22T09:04:25 at _Thread_Enable_dispatch() 2014-07-22T09:04:32 the new state of the task is STATES_DELAYING 2014-07-22T09:05:01 so it will block 2014-07-22T09:05:02 But, where is the part it's storing task registers? 2014-07-22T09:05:23 eventually, the scheduler picks a different thread to run, maybe idle thread, and does the context switch to it. 2014-07-22T09:05:30 that context switch will save the regs. 2014-07-22T09:06:23 But this way the context would be touched by the calls of rtems_wake_after and other calls from there 2014-07-22T09:06:52 OK another question, How can I debug and get a peak into the chain of tasks at anytime? 2014-07-22T09:07:06 from GDB 2014-07-22T09:07:11 If feasible 2014-07-22T09:09:34 umm 2014-07-22T09:09:43 you can. 2014-07-22T09:10:04 i used to have some gdb helpers for that, but i might not have those anymore. 2014-07-22T09:10:32 are you referring to the chain of watchdog tasks? 2014-07-22T09:11:12 No, the tasks that the scheduler pick from when dispatch_necessary is true 2014-07-22T09:11:57 watchdog tasks are properly added/removed now 2014-07-22T09:12:32 ah 2014-07-22T09:13:24 If you happen to find out how I can use these GDB helpers, please let me know 2014-07-22T09:13:48 that chain is located via the Scheduler_Control structure in the scheduler operations 2014-07-22T09:13:57 i think my helpers are probably outdated anyway 2014-07-22T09:14:17 for the priority scheduler... 2014-07-22T09:14:33 Thanks, I can reach it from GDB 2014-07-22T09:15:14 you'll want the Scheduler_priority_Node Priority; field 2014-07-22T09:15:39 this is defined in cpukit/sapi/include/confdefs.h 2014-07-22T09:15:56 rather that is where you can find the Scheduler_Control 2014-07-22T09:15:58 That's the default scheduler right ? 2014-07-22T09:16:02 yes 2014-07-22T09:16:23 I can get from Scheduler_Control and see what I can do 2014-07-22T09:16:24 the Scheduler_priority_Node is defined in cpukit/score/include/rtems/score/schedulerpriority.h 2014-07-22T09:16:37 Thanks 2014-07-22T09:16:37 Would you mind if I asked one last question? 2014-07-22T09:17:06 I am allocating the exception stack manually from task stack, should the stack pointer be modified to point to the previous task stack pointer before calling _Thread_Dispatch ? And how this stack should be affected when calling the C handler and when jumping to _ISR_Dispatch 2014-07-22T09:18:13 RTEMS defines an ISR stack for use 2014-07-22T09:18:27 you should be switching off the preempted task's stack to the ISR stack, unless it is nested ISRs 2014-07-22T09:18:57 I am using just two level of ISRs 2014-07-22T09:19:00 disable/enable 2014-07-22T09:19:37 According to the online manual, I can allocate the exception stack manually from the interrupted task stack 2014-07-22T09:20:26 uh, where does it say that? 2014-07-22T09:21:05 this is not generally permitted in RTEMS, because it is quite wasteful since you need to now reserve enough interrupt stack space on every regular task stack 2014-07-22T09:21:06 *** DrJoel has joined #rtems 2014-07-22T09:21:06 *** DrJoel has joined #rtems 2014-07-22T09:21:06 *** ChanServ sets mode: +o DrJoel 2014-07-22T09:21:30 hey DrJoel read back the log if you like..i'm chatting with Hesham about his work. 2014-07-22T09:22:06 I remember I read this option, along with RTEMS managing its interrupt stack 2014-07-22T09:22:09 Hi DrJoel 2014-07-22T09:22:59 hey.. runnign late.. sorry 2014-07-22T09:23:19 http://www.rtems.org/onlinedocs/releases/rtemsdocs-4.6.2/share/rtems/html/porting/porting00027.html 2014-07-22T09:23:34 f the CPU does not support a dedicated interrupt stack, then the porter has two options: (1) execute interrupts on the stack of the interrupted task, and (2) have RTEMS manage a dedicated interrupt stack. 2014-07-22T09:23:50 uhh, tha tis quite old documentation for rtems version 4.6 2014-07-22T09:24:07 we prefer now to have a dedicated interrupt stack 2014-07-22T09:24:38 OK that might be the problem 2014-07-22T09:25:05 *** Sched has quit IRC () 2014-07-22T09:25:07 DrJoel: I have updated ISR related code 2014-07-22T09:25:22 Awesome! So is ticker working? 2014-07-22T09:25:49 gedare: Do you know any of ports that do not have a dedicated stack. 2014-07-22T09:25:54 Not yet, but _Thread_Delay_ended is working as expected as well as _Watchdog_Remove 2014-07-22T09:26:01 gedare: do you have time to discuss the i386 patch I send? 2014-07-22T09:26:36 I was discussing with gedare about the problem why context switch is not done correctly 2014-07-22T09:27:22 The end of an ISR that requires a context switch is always a bit magic and architecture specific. 2014-07-22T09:27:44 Yes, regarding that.... 2014-07-22T09:27:52 The decision to do it is fairly straight forward but the stack/register manipulation can be tricky to figure out. 2014-07-22T09:28:04 _ISR_Dispatch is called three times after _Thread_Delay_ended 2014-07-22T09:28:45 is this the expected behavior ? 2014-07-22T09:29:41 No. It usually readies all three tasks (TA[123]). But it should be called once to switch to one of the three tasks (probably TA1 the first time). 2014-07-22T09:29:43 I mean after every call to _Thread_Delay_ended 2014-07-22T09:30:19 Oh.. then you forgot to increment ISR nest level and dispatch disable level. 2014-07-22T09:30:29 I did 2014-07-22T09:30:39 But not in ISR_Dispatch 2014-07-22T09:31:03 Should I increment them before ISR_Dispatch ? 2014-07-22T09:31:10 *** AoLaD has quit IRC () 2014-07-22T09:31:18 Let me check another port. Hold on. 2014-07-22T09:31:23 OK 2014-07-22T09:32:36 Please note that I am incrementing them using hard-code (temporary) that modifies _Per_CPU_Information structure 2014-07-22T09:33:01 No. Should both isr nest level and dispatch disable level should be 0 when you do the _ISR_Dispatch patch based on m68k . But DISPATCH_NEEDED should be true 2014-07-22T09:33:41 The m68k is the easiest code to read for the logic. Keep it up in a window and compare it. :) 2014-07-22T09:33:57 If you can pull it up now, I can walk you through it 2014-07-22T09:33:59 Yes, that's what happens with my code 2014-07-22T09:34:35 I have imitated it 2014-07-22T09:34:53 It's pulled always pulled up 2014-07-22T09:35:22 phipse: i'll try to take another look. I'm wondering if we can just put everything into the Pok BSP though 2014-07-22T09:35:29 Possibly you didn't "do the magic" with the return address/stack frame when you "turn the CPU inside out" and trick it to return from the ISR and look like the interrupted thread called _Thread_Disaptch. If at the end of _ISR_Dispatch, the return address is not right, you could end up there again. 2014-07-22T09:35:36 by providing the correct cpukit/score/cpu defines to let the BSP override the defaults. 2014-07-22T09:36:15 *** asuolen has quit IRC (Quit: Lost terminal) 2014-07-22T09:36:39 DrJoel: Ah, regarding that, I did the magic regarding the return address 2014-07-22T09:37:14 I suspect I am returning the stack/frame pointers wrong as I am allocating the exception stack manually 2014-07-22T09:37:24 Trust me .. it is hard to write that code correctly. I have spent a lot of time over the years with gdb, looking at register sets and stacks 2014-07-22T09:37:55 I hope it will not take years :) 2014-07-22T09:38:19 So, what is the best way to debug/handle this issue? 2014-07-22T09:39:08 gedare: okay, I just want to get it working, to only maintain virtualpok, and have a realativly fixed cpu implementation 2014-07-22T09:39:08 I was thinking of re-writing the whole ISR handlers routines using their fast context-switch feature 2014-07-22T09:39:08 on a CPU without register windows (shudder), you can usually figure this out by single stepping in asm and watching it the values you think should be in place, actually are. Walk out from the clock tick that calls _Thread_Delay_ended. Watch the stack, ensure callee clobbered are saved before calling _ISR_Dispatch, and watch the status register to see it is doing what you think. 2014-07-22T09:39:28 *** ppisa has quit IRC (Read error: Connection reset by peer) 2014-07-22T09:39:30 gedare: but we can discuss this on the list. 2014-07-22T09:39:53 Get it working without their magic first. When it works, we can see if that is useful. I ahve yet to see an architecture where it helped. :( 2014-07-22T09:40:10 It didn't meld nice with the OS requirements. 2014-07-22T09:40:27 I see 2014-07-22T09:40:47 Single step and ask questions. 2014-07-22T09:40:53 So, before jumping to _Thread_Dispatch 2014-07-22T09:40:59 Sorry about getting excited on the tools and pushing through the patches 2014-07-22T09:41:07 Should the stack pointer be of the interrupted task? 2014-07-22T09:41:37 It's really OK 2014-07-22T09:41:38 at which point? 2014-07-22T09:41:44 byebye 2014-07-22T09:41:52 Just before calling _Thread_Dispatch 2014-07-22T09:41:57 from _ISR_Handler 2014-07-22T09:42:07 You should be on the interrupted task stack (likely IDLE) 2014-07-22T09:42:10 *** phipse has quit IRC (Quit: leaving) 2014-07-22T09:43:00 So, should the stack pointer be of the IDLE tasks or the modified one from the exception handler ? 2014-07-22T09:43:08 Let me make it clearer 2014-07-22T09:43:50 This file is the core of our discussion -> https://github.com/heshamelmatary/rtems-gsoc2014/blob/or1k/cpukit/score/cpu/or1k/or1k-exception-handler-low.S 2014-07-22T09:44:32 It's just "experimental" until I get ticker working, and I would clean it up 2014-07-22T09:44:59 I need to read the architecture manual on exceptions/IRQs before I comment. That is still on my list unfortunately. :( 2014-07-22T09:45:31 Just single step and watch the registers. I can create a simpler version of ticker if you need one. 2014-07-22T09:45:35 So, _OR1K_Exception_Process is called from there -> https://github.com/heshamelmatary/rtems-gsoc2014/blob/or1k/c/src/lib/libbsp/or1k/or1ksim/start/start.S 2014-07-22T09:45:46 One task. One wake after. :) 2014-07-22T09:46:11 That's a good idea 2014-07-22T09:46:26 Then every 5 seconds, it will only switch from IDLE -> IRQ -> TA1, print, and TA1 -> IDLE, ... 2014-07-22T09:46:27 I would continue debugging from there 2014-07-22T09:46:46 Just don't call start on the TA2 and TA3. No reason to do more than that 2014-07-22T09:47:21 Great, I hope this issue won't take more time than that 2014-07-22T09:47:28 Thanks for your help 2014-07-22T09:47:49 Do you need to do anything regarding patches? 2014-07-22T09:48:27 Do you need me* 2014-07-22T09:50:28 I need to read the email thread and see what's up there. I am hoping we can do all that quickly by email. 2014-07-22T09:50:57 I haven't seen Christian's reaction to the config.gcc rework. :) 2014-07-22T09:52:13 He's happy with it, I think :) 2014-07-22T09:55:55 *** JustJanek has quit IRC (Quit: Leaving) 2014-07-22T10:27:05 *** Hesham has quit IRC (Quit: Leaving.) 2014-07-22T12:08:47 *** DrJoel has quit IRC (Quit: I used to think I was indecisive, but now I'm not too sure.) 2014-07-22T12:43:26 *** edwardk has quit IRC (Quit: Computer has gone to sleep.) 2014-07-22T13:14:11 *** monstr has quit IRC (Remote host closed the connection) 2014-07-22T14:01:18 *** atgreen has joined #rtems 2014-07-22T14:03:07 *** atgreen` has joined #rtems 2014-07-22T14:03:20 *** atgreen has quit IRC (Remote host closed the connection) 2014-07-22T14:03:21 *** atgreen` has quit IRC (Remote host closed the connection) 2014-07-22T14:09:39 *** atgreen has joined #rtems 2014-07-22T14:20:14 *** atgreen has quit IRC (Remote host closed the connection) 2014-07-22T14:20:56 *** atgreen has joined #rtems 2014-07-22T15:53:11 *** gedare has quit IRC (Quit: Leaving) 2014-07-22T16:39:33 *** kiwichris has quit IRC (Ping timeout: 252 seconds) 2014-07-22T16:58:58 *** kiwichris has joined #rtems 2014-07-22T17:02:17 *** kiwichri_ has joined #rtems 2014-07-22T17:03:30 *** kiwichris has quit IRC (Read error: Connection reset by peer) 2014-07-22T17:11:02 *** atgreen has quit IRC (Ping timeout: 260 seconds) 2014-07-22T18:04:36 *** Hesham has joined #rtems 2014-07-22T19:27:54 *** edwardk has joined #rtems 2014-07-22T19:36:27 *** edwardk has quit IRC (Ping timeout: 255 seconds) 2014-07-22T20:18:09 *** atgreen has joined #rtems 2014-07-22T20:20:53 *** Hesham has quit IRC (Quit: Leaving.) 2014-07-22T21:23:14 *** matttttt has joined #rtems 2014-07-22T21:31:02 *** matttttt has quit IRC (Quit: Page closed) 2014-07-22T22:02:00 *** Hesham has joined #rtems 2014-07-22T22:54:52 *** Hesham has quit IRC (Quit: Leaving.) 2014-07-22T23:51:22 *** monstr has joined #rtems 2014-07-23T00:22:56 *** monstr has quit IRC (Remote host closed the connection) 2014-07-23T01:21:13 hm, I wonder what time it is in the netherlands... 2014-07-23T01:34:04 *** edwardk has joined #rtems 2014-07-23T02:43:47 *** monstr has joined #rtems 2014-07-23T02:51:52 *** Hesham has joined #rtems 2014-07-23T03:01:51 *** edwardk has quit IRC (Quit: Computer has gone to sleep.) 2014-07-23T03:02:54 *** edwardk has joined #rtems 2014-07-23T03:16:07 *** kiwichri_ has quit IRC () 2014-07-23T03:44:32 *** zoso has joined #rtems 2014-07-23T03:51:52 *** kiwichris has joined #rtems 2014-07-23T04:47:47 *** edwardk has quit IRC (Quit: Computer has gone to sleep.) 2014-07-23T04:53:52 *** edwardk has joined #rtems 2014-07-23T05:14:47 bmatt: 8:21 when you wrote that :) 2014-07-23T05:55:05 how’s the ethernet on BB rtems? :-) 2014-07-23T05:58:28 *** Hesham has quit IRC (Quit: Leaving.) 2014-07-23T06:05:42 *** zoso has quit IRC (Read error: Connection reset by peer) 2014-07-23T06:09:56 *** zoso has joined #rtems 2014-07-23T06:14:06 *** zoso has quit IRC (Read error: Connection reset by peer) 2014-07-23T07:00:38 *** jenniferA has quit IRC (Quit: Leaving) 2014-07-23T07:00:52 *** Sched has joined #rtems 2014-07-23T07:05:02 *** Sched has quit IRC (Client Quit) 2014-07-23T07:12:33 *** freenix has joined #rtems 2014-07-23T07:13:17 hi kiwichris 2014-07-23T07:17:27 *** atgreen has quit IRC (Ping timeout: 256 seconds) 2014-07-23T07:46:00 *** Hesham has joined #rtems 2014-07-23T08:04:10 *** freenix has quit IRC (Ping timeout: 246 seconds) 2014-07-23T08:11:36 *** edwardk has quit IRC (Quit: Computer has gone to sleep.) 2014-07-23T08:54:21 *** monstr has quit IRC (Remote host closed the connection) 2014-07-23T09:04:14 *** Hesham has quit IRC (Quit: Leaving.) 2014-07-23T09:42:05 *** matttttttttt has joined #rtems 2014-07-23T09:42:09 *** matttttttttt has left #rtems 2014-07-23T09:52:15 peerst: i'm merging (submitting) the BB rtems first :) 2014-07-23T09:52:34 actually, volunteers are wanted to sanity-check my blogpost with all the details 2014-07-23T09:52:40 beng-nl: sure 2014-07-23T09:52:45 blogpost? 2014-07-23T09:53:10 where? 2014-07-23T09:53:19 yeah i just wrote it yesterday, for people with no necessary prior knowledge of rtems but with a device they want to build & run it on 2014-07-23T09:53:25 not unlike myself, to be honest ;) 2014-07-23T09:53:27 http://www.shrike-systems.com/beagleboard-xm-beaglebone-black-and-everything-else-rtems-on-the-beagles.html 2014-07-23T09:54:08 well I can’t help with the not prior use of RTEMS part but I deffo will read it and follow along 2014-07-23T09:54:26 great 2014-07-23T09:54:33 i also like it to be nice to read etc 2014-07-23T09:56:44 beng-nl: regarding nice to read http://imgur.com/7GR9ccM 2014-07-23T09:57:05 the black on dark bluegreen doesn’t come out well on my screen 2014-07-23T09:57:17 :( 2014-07-23T09:57:22 no it's awful on mine too :S 2014-07-23T09:57:30 ah ok 2014-07-23T09:57:49 maybe there is a switch to map black to white for dark backgrounds 2014-07-23T09:57:51 ? 2014-07-23T09:58:35 oh its just CSS classes … easy 2014-07-23T10:00:41 *ogle* 2014-07-23T10:00:58 it seems color for class n isn’t set 2014-07-23T10:01:20 shouldn't ".highlight .n { color: #93a1a1 } /* Name */" hit? 2014-07-23T10:02:32 nah it doesn’t hit 2014-07-23T10:02:41 the color gets inherited from body 2014-07-23T10:03:18 interestingly .highlight .c hits for those spans 2014-07-23T10:03:43 some typo? 2014-07-23T10:03:49 *headscratch* 2014-07-23T10:04:02 first foray into css.. 2014-07-23T10:04:14 fun 2014-07-23T10:05:06 you have a browser where you can see the CSS cascade in a window? 2014-07-23T10:05:13 kinda, i have element inspector in FF 2014-07-23T10:05:58 I looked with inspector from safari 2014-07-23T10:06:33 i also see .n no hitting but e.g. .mi does but i can't see the difference as yet 2014-07-23T10:06:46 eh there is no .highlight .n in your pygments.css 2014-07-23T10:07:46 which is where yur .c color comes from 2014-07-23T10:07:52 gasp yes.. i was looking at the wrong file ok 2014-07-23T10:09:22 grrr 2014-07-23T10:10:20 ok i copied over the file i was looking at :) 2014-07-23T10:10:23 looks better now 2014-07-23T10:12:19 peerst: thanks for helping/making me find that 2014-07-23T10:13:21 much better 2014-07-23T10:13:32 looks good 2014-07-23T10:14:13 beng-nl: I will try to follow this on my freebsd vagrant box 2014-07-23T10:14:26 mmm drat 2014-07-23T10:14:47 ? 2014-07-23T10:14:48 for me that fails on building one of the msdos fs utils :( 2014-07-23T10:14:57 in the RSB beagle bset step 2014-07-23T10:15:05 i guess i have to fix that anyway 2014-07-23T10:15:06 FreeBSD? 2014-07-23T10:15:07 yeah 2014-07-23T10:15:16 it's my favourite too, although you can hardly tell nowadays 2014-07-23T10:15:21 will look into it, maybe I can help 2014-07-23T10:15:27 cool, thanks! 2014-07-23T10:15:51 worryingly, dosfstools isn't in /usr/ports/ 2014-07-23T10:16:10 hm 2014-07-23T10:16:25 it can't be especially os-dependent now can it.. 2014-07-23T10:17:54 what do you need it for? 2014-07-23T10:18:07 just building a dos fs and populate it 2014-07-23T10:18:10 making the SD card FS image to boot an RTEMS executable, yeah 2014-07-23T10:19:23 well I use something like this on FreeBSD http://ideone.com/wDAHpZ 2014-07-23T10:19:41 but its not portable to linux 2014-07-23T10:19:49 :/ 2014-07-23T10:19:56 yeah that's pretty os-specific 2014-07-23T10:20:10 admittedly so is dosfstools 2014-07-23T10:20:36 maybe there is no portable easy way to make a fat filesystem image 2014-07-23T10:21:22 we have not yet begun to fight 2014-07-23T10:21:53 :-) 2014-07-23T10:22:16 but I will not be stuck on the fat filesystem stuff since I have my own ways 2014-07-23T10:22:32 okay, i guess you can comment out the dosfstools in the beagle bset 2014-07-23T10:22:53 yep 2014-07-23T10:22:57 i want to provide an out-of-the-box everything-works experience, you see 2014-07-23T10:23:16 which is great 2014-07-23T10:23:30 and so much better than any platform RTEMS runs on so far 2014-07-23T10:23:47 music to my ears! 2014-07-23T10:24:09 otherwise it's such a fragile part of the process 2014-07-23T10:24:10 and what I find especially great is that I can build upon it to get the same experience for Grisp 2014-07-23T10:24:57 this is a big issue getting new people to RTEMS 2014-07-23T10:26:24 yeah i can imagine 2014-07-23T10:26:34 it's enough of a jungle as it is for newcomers 2014-07-23T10:26:43 all the commercial users don’t care about stuff like beagle bone 2014-07-23T10:26:45 then you have an ELF and 'good luck' 2014-07-23T10:26:49 (afaik) 2014-07-23T10:26:52 yeah 2014-07-23T10:27:19 or maybe a old description to get it running on a 500$ deval board 2014-07-23T10:27:23 eval 2014-07-23T10:27:40 which would be fine for me as commercial dev 2014-07-23T10:27:44 dosfstools is shameful in is linux-onliness 2014-07-23T10:27:51 is* 2014-07-23T10:27:52 its* 2014-07-23T10:27:55 peerst: yeah 2014-07-23T10:28:07 but I’m spoilt anyway since eb builds my hardware for me 2014-07-23T10:28:18 and I get it up and running with a RTEMS on 2014-07-23T10:28:28 as it should be ;-) 2014-07-23T10:29:15 yeah I used to do this getting it out of reset with rtems before too 2014-07-23T10:29:27 but I prefer this kind of work sharing 2014-07-23T10:30:39 ah fun comming up https://twitter.com/ISEE3Reboot/status/491968242965958656 2014-07-23T11:07:49 *** atgreen has joined #rtems 2014-07-23T11:08:05 good morning beng-nl and peerst :) 2014-07-23T11:08:13 hey bmatt :-) 2014-07-23T11:08:15 hah morning 2014-07-23T11:08:39 i am just trying to ditch dosfstools. mtools has an mformat 2014-07-23T11:08:43 it's morning here in the center of the universe, the san francisco bay area :) 2014-07-23T11:08:49 ha-ha ;-) 2014-07-23T11:09:03 dosfstools is awful 2014-07-23T11:10:56 bmatt: i have tuned the post with all your feedback, thank you 2014-07-23T11:11:49 mtools is the one thats been here forever 2014-07-23T11:11:57 and its portable 2014-07-23T11:12:23 yeah 2014-07-23T11:12:51 i was already using it in scrips in rtems, i didn't realize it had an mformat too 2014-07-23T11:12:56 I have mtools in FreeBSD ports collection and MacPorts 2014-07-23T11:13:07 if that works.. no reason to use stupid dosfstools 2014-07-23T11:13:10 what a bitter experience 2014-07-23T11:13:12 *** atgreen has quit IRC (Ping timeout: 245 seconds) 2014-07-23T11:13:28 and dosfstools in neither 2014-07-23T11:22:21 fuuck 2014-07-23T11:22:44 (this is the sound of my setup improving without dosfstools) 2014-07-23T11:22:51 (in the 'break eggs' phase of omelet making) 2014-07-23T11:39:25 oeh looking good now 2014-07-23T11:39:59 *** atgreen has joined #rtems 2014-07-23T11:54:15 ok done.. it seems 2014-07-23T12:41:40 *** atgreen has quit IRC (Ping timeout: 260 seconds) 2014-07-23T14:06:45 *** atgreen has joined #rtems 2014-07-23T16:48:29 *** atgreen has quit IRC (Ping timeout: 250 seconds) 2014-07-23T17:35:26 *** atgreen has joined #rtems 2014-07-23T18:02:40 I need a bigger system 2014-07-23T18:02:55 4 cores and spinning disk isn't enough for this 2014-07-23T18:03:14 full build-test-destroy cycles take like 5 hours 2014-07-23T18:14:08 ouch 2014-07-23T18:14:34 how long does your test (qemu) take? 2014-07-23T18:14:50 for me it's 30 mins on laptop, 1 hour on a rented server i have 2014-07-23T19:03:26 *** kiwichris has quit IRC () 2014-07-23T19:10:06 beng-nl: hey quick typo in your blog post 2014-07-23T19:10:41 cd $HOME/development/rtems/rtems-src/c... should be cd $HOME/development/rtems/sources/rtems-src/c... in the "Writing an SD card" section 2014-07-23T19:13:47 ogle 2014-07-23T19:15:09 i... didn't intend that layout actually 2014-07-23T19:15:19 rtems-src is cloned in development/rtems/ , no? 2014-07-23T19:15:35 the sources is just the RSB subdir 2014-07-23T19:19:53 *** kiwichris has joined #rtems 2014-07-23T19:22:51 ah, oops. looks like I got mixed up then 2014-07-23T19:35:34 *** Hesham has joined #rtems 2014-07-23T19:36:54 pff time to submit i'd say 2014-07-23T19:37:03 what do you think bmatt 2014-07-23T19:37:22 beng-nl: I say hold it hostage 2014-07-23T19:37:26 until peerst releases his code! 2014-07-23T19:37:29 muhahahahahaha 2014-07-23T19:37:31 hahaha :) 2014-07-23T19:50:49 ok writing a submit email now 2014-07-23T19:50:51 exciting 2014-07-23T20:02:09 ok done 2014-07-23T20:10:41 =D 2014-07-23T20:16:55 missed the email by about 14 minutes 2014-07-23T20:16:59 looks good! 2014-07-23T23:35:38 *** peerst_ has joined #rtems 2014-07-23T23:36:35 *** peerst has quit IRC (Read error: Connection reset by peer) 2014-07-23T23:36:35 *** peerst_ is now known as peerst 2014-07-23T23:50:55 *** monstr has joined #rtems 2014-07-23T23:58:03 *** Hesham has quit IRC (Quit: Leaving.) 2014-07-24T01:44:56 *** edwardk has joined #rtems 2014-07-24T02:31:07 *** edwardk has quit IRC (Quit: Computer has gone to sleep.) 2014-07-24T02:43:27 bmatt: if we play this game … I don’t release without ethernet working in RTEMS ;-) 2014-07-24T02:44:02 thats half serious btw 2014-07-24T02:44:34 People using Erlang want to network the stuff to run distributed 2014-07-24T02:44:48 And to run embedded webservers and other services 2014-07-24T03:11:16 *** kiwichris has quit IRC () 2014-07-24T03:24:27 *** zoso has joined #rtems 2014-07-24T04:04:05 *** kiwichris has joined #rtems 2014-07-24T04:09:55 beng-nl, patch looks good; just waiting for seb ok 2014-07-24T04:27:08 *** zoso has quit IRC (Ping timeout: 260 seconds) 2014-07-24T04:54:29 kiwichris: great news! thanks for looking so quickly. i hope the one patch, two commits post was clear enough. 2014-07-24T06:09:04 *** edwardk has joined #rtems 2014-07-24T06:32:52 *** edwardk has quit IRC (Ping timeout: 240 seconds) 2014-07-24T08:51:09 *** monstr has quit IRC (Remote host closed the connection) 2014-07-24T08:55:11 *** atgreen has quit IRC (Ping timeout: 264 seconds) 2014-07-24T09:21:21 *** Hesham has joined #rtems 2014-07-24T09:26:45 *** Hesham has quit IRC (Quit: Leaving.) 2014-07-24T09:28:30 bmatt: glad you like it! (btw) 2014-07-24T09:35:04 *** edwardk has joined #rtems 2014-07-24T09:39:54 *** edwardk has quit IRC (Read error: Connection reset by peer) 2014-07-24T10:30:47 peerst: that's fine and all, but I can't promise to be successful in getting ethernet working and my particular use case doesn't require ethernet at all 2014-07-24T10:31:02 so it's a pretty big diversion for me :) 2014-07-24T10:32:33 Erlang without Ethernet is quite useless 2014-07-24T10:32:49 respectfully, I disagree 2014-07-24T10:32:56 How would you remote shell into your Erlang on RTEMS node? 2014-07-24T10:33:03 I wouldn't 2014-07-24T10:33:06 I don't need to :) 2014-07-24T10:33:44 Well then you loose most of the productivity gain you get from having a Erlang on RTEMS 2014-07-24T10:33:51 youc can’t try stuff 2014-07-24T10:33:54 again, I disagree 2014-07-24T10:33:57 I dont' need to try stuff 2014-07-24T10:34:00 I've got a working codebase 2014-07-24T10:34:01 you can use common test to run tess 2014-07-24T10:34:15 tests 2014-07-24T10:34:36 running dbg/trace on serial console is not feasible 2014-07-24T10:35:06 maybe not for you 2014-07-24T10:35:08 bmatt: well its easy: I see no value for 99% of Erlang on RTEMS users when there is no network 2014-07-24T10:35:23 luckily for me, I'm not 99% of Erlang on RTEMS users :) 2014-07-24T10:35:25 and I need the network to debug bringing it up 2014-07-24T10:36:02 I’m not gong back to running erlang shell on a console 2014-07-24T10:36:11 with no commandline editing 2014-07-24T10:36:21 peer, I'm not asking you to debug anything or go back to running erlang shell on a console or anything else 2014-07-24T10:36:31 all I'm asking is for you to release your work to the wild 2014-07-24T10:36:46 bmatt: I won’t realease anything that doesn’t work period 2014-07-24T10:36:59 * bmatt shrugs 2014-07-24T10:37:03 I'm sad to hear that 2014-07-24T10:37:20 because it means I'm going to have to start working on duplicating something that's already working 2014-07-24T10:37:26 and that's a huge waste of time 2014-07-24T10:37:34 well I will eventuall build a ethernet driver, but it will take longer 2014-07-24T10:52:58 just send him your code in a tarball if he needs it 2014-07-24T10:53:17 if you think it's of no value and he things he needs it, then just send it 2014-07-24T10:53:42 it contains non open source parts and needs fixing and porting to beaglebone 2014-07-24T10:53:56 bmatt wanted to help with this 2014-07-24T10:54:06 so far I only hear nagging 2014-07-24T10:54:22 I nag at your request 2014-07-24T10:54:28 but I'll stop now 2014-07-24T10:54:36 consider the matter closed 2014-07-24T10:54:59 when I said that I as assuming ethernet working 2014-07-24T10:55:49 I know you think different but I’m working with Erlang on RTEMS now for over 2 years 2014-07-24T10:56:18 and for developemt network is essntial 2014-07-24T10:57:04 otherwise you are caoght in a build release copy it to flash start, crash cycle 2014-07-24T10:57:26 and believe me it does crash until Erlang/OTP is fully running 2014-07-24T10:57:55 peerst: release, or don't release, but don't feel you need to justify anything to me 2014-07-24T10:58:27 I don’t want to justify, I want you to understand the necessity of network 2014-07-24T10:58:54 I'll work on Ethernet as I have time and as I'm capable, and according to my own needs 2014-07-24T10:59:26 I need some time to clean up my OTP patches anyway 2014-07-24T10:59:56 in meantime I will try out whats working so far on BB 2014-07-24T14:05:20 *** atgreen has joined #rtems 2014-07-24T14:17:15 *** atgreen has quit IRC (Ping timeout: 256 seconds) 2014-07-24T14:19:43 *** atgreen has joined #rtems 2014-07-24T15:48:59 *** edwardk has joined #rtems 2014-07-24T16:40:47 *** atgreen has quit IRC (Ping timeout: 264 seconds) 2014-07-24T17:38:23 *** kiwichris has quit IRC () 2014-07-24T17:55:05 *** kiwichris has joined #rtems 2014-07-24T17:55:18 beng-nl, hi 2014-07-24T19:36:22 *** Hesham has joined #rtems 2014-07-24T21:16:01 *** Hesham has quit IRC (Ping timeout: 256 seconds) 2014-07-24T21:30:08 *** Hesham has joined #rtems 2014-07-24T21:33:18 *** Hesham has quit IRC (Client Quit) 2014-07-24T22:37:05 *** Hesham has joined #rtems 2014-07-24T23:18:55 *** Hesham has quit IRC (Quit: Leaving.) 2014-07-25T00:08:01 *** zoso has joined #rtems 2014-07-25T00:08:28 *** zoso has quit IRC (Read error: Connection reset by peer) 2014-07-25T00:10:38 *** monstr has joined #rtems 2014-07-25T00:18:23 *** monstr has quit IRC (Remote host closed the connection) 2014-07-25T00:20:33 *** Hesham has joined #rtems 2014-07-25T01:33:16 *** monstr has joined #rtems 2014-07-25T02:17:02 *** edwardk_ has joined #rtems 2014-07-25T02:17:08 *** edwardk has quit IRC (Remote host closed the connection) 2014-07-25T02:48:09 *** kiwichris has quit IRC () 2014-07-25T03:13:29 *** kiwichris has joined #rtems 2014-07-25T03:27:57 *** edwardk_ has quit IRC (Quit: Computer has gone to sleep.) 2014-07-25T03:31:44 *** edwardk has joined #rtems 2014-07-25T04:16:42 hi kiwichris! 2014-07-25T04:19:31 *** Hesham has joined #rtems 2014-07-25T04:33:56 *** Joff has joined #rtems 2014-07-25T04:42:46 *** Hesham has quit IRC (Quit: Leaving.) 2014-07-25T05:27:56 *** atgreen has joined #rtems 2014-07-25T06:14:49 *** Hesham has joined #rtems 2014-07-25T06:25:54 *** Hesham has quit IRC (Quit: Leaving.) 2014-07-25T06:42:32 beng-nl,hi 2014-07-25T07:31:40 *** Joff has quit IRC (Quit: Page closed) 2014-07-25T08:01:02 how are you, kiwichris? 2014-07-25T08:10:27 *** freenix has joined #rtems 2014-07-25T08:11:29 Hi kiwichris 2014-07-25T09:02:09 *** freenix has quit IRC (Quit: Leaving) 2014-07-25T10:10:43 *** kiwichris has quit IRC (Ping timeout: 272 seconds) 2014-07-25T10:11:19 *** kiwichris has joined #rtems 2014-07-25T10:27:27 *** edwardk has quit IRC (Quit: Computer has gone to sleep.) 2014-07-25T10:37:46 *** edwardk has joined #rtems 2014-07-25T10:46:53 *** edwardk has quit IRC (Quit: Computer has gone to sleep.) 2014-07-25T10:51:38 *** edwardk has joined #rtems 2014-07-25T11:11:16 *** edwardk has quit IRC (Quit: Computer has gone to sleep.) 2014-07-25T12:44:13 *** edwardk has joined #rtems 2014-07-25T12:57:07 *** edwardk has quit IRC (Quit: Computer has gone to sleep.) 2014-07-25T13:43:28 *** matttttttttt has joined #rtems 2014-07-25T13:43:44 *** matttttttttt has left #rtems 2014-07-25T14:14:12 *** edwardk has joined #rtems 2014-07-25T14:33:10 *** monstr has quit IRC (Remote host closed the connection) 2014-07-25T16:16:38 lo all 2014-07-25T16:21:23 *** peerst is now known as all 2014-07-25T16:21:35 lo beng-nl 2014-07-25T16:21:42 *** all is now known as peerst 2014-07-25T16:24:07 lo all :-) 2014-07-25T16:25:33 lo 2014-07-25T17:49:06 *** kiwichris has quit IRC () 2014-07-25T17:49:28 *** kiwichris has joined #rtems 2014-07-25T18:22:59 *** Schoumi_ has joined #rtems 2014-07-25T18:29:16 *** edwardk_ has joined #rtems 2014-07-25T18:29:28 *** edwardk has quit IRC (*.net *.split) 2014-07-25T18:29:29 *** Schoumi has quit IRC (*.net *.split) 2014-07-25T18:39:02 *** Hesham has joined #rtems 2014-07-25T20:16:59 *** cdesai has quit IRC (Ping timeout: 256 seconds) 2014-07-25T20:19:50 *** cdesai has joined #rtems 2014-07-25T21:12:39 *** Hesham1 has joined #rtems 2014-07-25T21:13:37 *** Hesham has quit IRC (Ping timeout: 245 seconds) 2014-07-25T23:14:39 *** edwardk_ is now known as edwardk 2014-07-25T23:17:05 *** Hesham1 is now known as Hesham 2014-07-25T23:43:37 *** kiwichris has quit IRC (Read error: Connection reset by peer) 2014-07-25T23:43:44 *** kiwichris has joined #rtems 2014-07-25T23:54:38 *** Hesham has quit IRC (Quit: Leaving.) 2014-07-26T00:34:13 *** Hesham has joined #rtems 2014-07-26T01:06:42 *** Hesham has quit IRC (Quit: Leaving.) 2014-07-26T01:26:05 *** atgreen` has joined #rtems 2014-07-26T01:29:24 *** atgreen has quit IRC (Ping timeout: 240 seconds) 2014-07-26T01:40:37 *** Hesham has joined #rtems 2014-07-26T04:20:50 *** Hesham has quit IRC (Quit: Leaving.) 2014-07-26T11:23:04 *** edwardk has quit IRC (Quit: Computer has gone to sleep.) 2014-07-26T12:04:36 *** edwardk has joined #rtems 2014-07-26T12:16:10 *** edwardk_ has joined #rtems 2014-07-26T12:16:29 *** edwardk has quit IRC (Ping timeout: 272 seconds) 2014-07-26T12:17:07 *** edwardk_ has quit IRC (Read error: Connection reset by peer) 2014-07-26T12:17:27 *** edwardk has joined #rtems 2014-07-26T12:22:00 *** edwardk has quit IRC (Ping timeout: 250 seconds) 2014-07-26T12:48:21 *** xMYTHICx has joined #rtems 2014-07-26T13:22:10 *** xMYTHICx has quit IRC (Quit: xMYTHICx) 2014-07-26T15:34:45 *** edwardk has joined #rtems 2014-07-26T15:51:32 *** edwardk has quit IRC (Quit: Computer has gone to sleep.) 2014-07-26T18:02:34 *** Hesham has joined #rtems 2014-07-26T18:11:15 *** Hesham has quit IRC (Quit: Leaving.) 2014-07-26T18:13:40 *** edwardk has joined #rtems 2014-07-26T18:42:08 *** Hesham has joined #rtems 2014-07-26T19:09:06 *** edwardk has quit IRC (Quit: Computer has gone to sleep.) 2014-07-26T19:20:52 *** edwardk has joined #rtems 2014-07-26T19:55:53 *** edwardk has quit IRC (Quit: Computer has gone to sleep.) 2014-07-26T19:56:34 *** edwardk has joined #rtems 2014-07-26T20:06:39 *** edwardk has quit IRC (Quit: Computer has gone to sleep.) 2014-07-26T20:53:05 *** Hesham has quit IRC (Quit: Leaving.) 2014-07-26T21:22:01 *** edwardk has joined #rtems 2014-07-26T21:56:24 *** edwardk has quit IRC (Quit: Computer has gone to sleep.) 2014-07-26T22:00:31 *** xMYTHICx has joined #rtems 2014-07-26T22:06:30 *** xMYTHICx has quit IRC (Quit: xMYTHICx) 2014-07-26T22:08:17 *** xMYTHICx has joined #rtems 2014-07-26T22:17:40 *** edwardk has joined #rtems 2014-07-26T22:26:24 *** Hesham has joined #rtems 2014-07-26T22:28:28 *** xMYTHICx has quit IRC (Quit: xMYTHICx) 2014-07-26T23:06:45 *** Hesham has quit IRC (Read error: No route to host) 2014-07-26T23:08:36 *** Hesham has joined #rtems 2014-07-26T23:44:36 *** edwardk has quit IRC (Quit: Computer has gone to sleep.) 2014-07-27T00:03:45 *** edwardk has joined #rtems 2014-07-27T04:12:35 *** Hesham has quit IRC (Ping timeout: 264 seconds) 2014-07-27T10:26:11 *** gigetoo has joined #rtems 2014-07-27T11:47:59 beng-nl: ahoy :) 2014-07-27T12:27:23 ahoy to you! 2014-07-27T12:30:42 just in time for me to log off =D 2014-07-27T12:31:16 I do have to run, but I'll pick RTEMS back up as soon as I ship these systems for work 2014-07-27T12:32:00 and I think I might have convinced a friend to work on the LAN8710A phy driver 2014-07-27T12:34:15 bbl :) 2014-07-27T13:34:52 sounds cool :-) 2014-07-27T16:11:00 lo all 2014-07-27T16:38:27 *** xMYTHICx has joined #rtems 2014-07-27T16:40:34 *** xMYTHICx has left #rtems 2014-07-27T16:43:42 *** xMYTHICx has joined #rtems 2014-07-27T16:45:20 *** xMYTHICx has quit IRC (Client Quit) 2014-07-27T16:49:11 *** xMYTHICx_ has joined #rtems 2014-07-27T17:40:09 *** kiwichris has quit IRC (Ping timeout: 272 seconds) 2014-07-27T17:53:29 *** kiwichris has joined #rtems 2014-07-27T19:25:20 *** atgreen` has quit IRC (Ping timeout: 250 seconds) 2014-07-27T20:30:16 *** kiwichris has quit IRC () 2014-07-27T20:50:36 *** kiwichris has joined #rtems 2014-07-27T21:06:21 *** kiwichris has quit IRC () 2014-07-27T21:35:02 *** kiwichris has joined #rtems 2014-07-27T22:03:08 *** atgreen has joined #rtems