**** BEGIN LOGGING AT Mon Jul 25 02:59:58 2016 Jul 25 13:08:12 amr_ragaey: maybe doing IRC is better than Skype? Jul 25 13:08:19 amragaey: ^^^ Jul 25 13:08:44 your state diagram seemed like it could use some improvement. Jul 25 13:09:07 I can tackle it right now, before I get distracted with other actions. Jul 25 13:09:41 amragaey: it is *VERY* difficult to understand what you are saying. Jul 25 14:54:16 mdp there? Jul 25 14:55:57 ds2 ,there? Had a doubt. Jul 25 14:56:17 in my setup function I am calling in the iowrite and ioread function and writing to a fixed location from where I read the configuration through my firmware. Jul 25 14:56:40 ds2, But I am still not clear as to how to get the config from userland. I mean what variable or buffer are these configs written to by the spi-subsystem? Jul 25 14:57:22 Also here :http://lxr.free-electrons.com/source/drivers/spi/spi-omap2-mcspi.c#L938 Jul 25 14:57:30 What is l? On reading the description, it seems to be something that allows reading and writing to the userland. But I am not sure Jul 25 16:07:02 ds2: there ? Jul 25 17:12:05 ds, mdp, if you see my questions, please do reply whenever free, I will check the logs. Jul 25 17:12:28 * chanakya_vc going afk. Be back after dinner Jul 25 17:50:41 ds2: ?? Jul 25 17:51:36 :) Jul 25 17:51:47 hi m_w ! Jul 25 17:51:58 hey ZeekHuge Jul 25 17:51:59 the clock is working .. Jul 25 17:52:07 what was the trick? Jul 25 17:52:42 well .. the buffer before the clock pin. Jul 25 17:53:10 The thing I was worried about was that the o/p is lower than 2.5 Jul 25 17:53:30 and the schematics say that is should be greater than that Jul 25 17:53:59 but that was ADC IC's data sheet Jul 25 17:54:16 as long as it works, I would leave it alone Jul 25 17:54:35 and the buffer in the ADC board makes it easy by even accepting lower voltages Jul 25 17:55:28 I tried other higher resistors too and they were working .. but finally used 100ohms as ds2 suggested Jul 25 17:56:13 but now, the data. ADC doesn’t seem to give out the data. Jul 25 17:57:07 all its o/p data pin remain at ~2.2V even when I am changing the input Jul 25 18:10:45 oh no Jul 25 18:11:04 lemme see if we missed some control lines Jul 25 18:16:10 JP1 should be GND Jul 25 18:16:28 JP2 should be GND Jul 25 18:18:07 J2 pin 39 should be VCC Jul 25 18:27:30 as I always say .. m_w you are a life saver .. Jul 25 18:27:34 it seems to work Jul 25 18:27:45 pin 39 is what i was missing Jul 25 18:28:18 yay Jul 25 18:29:39 I do what I do Jul 25 18:45:10 hmmm Jul 25 18:46:09 ZeekHuge: can you probe the clock at the chip to make sure it goes above and below the Vih and Vil thresholds respectively? Jul 25 18:46:49 (Be in and out, many misc. errands today - will check in periodically) Jul 25 19:26:09 DMA ... Jul 25 19:29:04 Linux dma allows transfer caused by the interruption? Jul 25 19:31:09 the transfer one word and the next words after the interruption Jul 25 19:49:36 anyone who has any hints I asked to betray the DMA secret Jul 25 20:30:40 ds2: Jul 25 20:30:59 the buffer goes HIGH upto 3.2 Jul 25 20:31:03 almost Jul 25 20:31:15 and Low as to 0.2 Jul 25 20:31:39 according to the datasheet, it looks okay Jul 25 20:31:56 I need to check the LOW again .. just a second. Jul 25 20:43:58 Wormo_: my BBB is saying that the filesystem is mounted as read only .. Jul 25 20:44:01 suddenly ? Jul 25 20:44:22 I just changed the dts in the /boot/uEnv.txt Jul 25 20:44:43 ds2: m_w ^^ Jul 25 21:05:57 ZeekHuge: cat /proc/cmdline Jul 25 21:06:01 I checked it earlier ... the buffer output was going LOW to about 0.something V ( it was probably 0.2 ) but now its not. :( :( :( Jul 25 21:06:14 m_w: reboot and it was okay then ... Jul 25 21:06:32 okay but now something else is broken? Jul 25 21:06:50 yeah ... dont know what .. Jul 25 21:08:13 loose connection? Jul 25 21:09:47 ZeekHuge: Is the PRU you are using on the LCD pins or on the eMMC pins? Jul 25 21:13:01 ds2: its on the LCD pins Jul 25 21:21:07 ZeekHuge: did the values of the 2 signals on the ADC itself look reasonable? Jul 25 21:21:58 okay got it back working Jul 25 21:23:28 ds2: So the the output of the buffer is HIGH = 3.13 and LOW = 0.12 . The ADC IC's datasheet says that Vih > 2 and Vil < 0.8 Jul 25 21:23:36 so it is okay. right ? Jul 25 21:24:08 and these measure are at a very low frequency for now. Jul 25 21:31:58 and this is the code I am using to test if the data is coming out ... https://github.com/ZeekHuge/BeagleScope/blob/wip/examples/firmware_exmples/pru_pin_state_reader/PRU_PIN_STATE_READER/main.c#L91 Jul 25 21:32:05 and it seems that it isnt. Jul 25 21:33:17 Actually earlier, when m_w pointed out the J2 pin 39 error I was doing very raw test, and it was looking like ADC was working .. Jul 25 21:33:49 but after soldering up all .. it looks as if it is not working Jul 25 21:42:20 connectivity checks of the newly soldered parts? continuous where it should be, no shorts between neighboring? Jul 25 21:42:28 ZeekHuge ^^^ Jul 25 21:46:43 cold solder maybe? Jul 25 22:02:30 Okay so my test was using only last 6 bits from the ADC and I used this code : https://github.com/ZeekHuge/BeagleScope/blob/wip/examples/firmware_exmples/pru_pin_state_reader/PRU_PIN_STATE_READER/main.c#L91 Jul 25 22:02:47 and then, I used 2 reference points Jul 25 22:02:52 1. ground Jul 25 22:04:01 2. one that i created using a variable resistor Jul 25 22:04:27 for each of them the command that I executed was : Jul 25 22:04:46 echo a >/dev/rpmsg_pru31 && xxd -c 4 /dev/rpmsg_pru31 Jul 25 22:05:11 the output for ground was : Jul 25 22:05:13 0000cb8: d300 0000 .... Jul 25 22:05:13 0000cbc: d000 0000 .... Jul 25 22:05:13 0000cc0: ec00 0000 .... Jul 25 22:05:13 0000cc4: f000 0000 .... Jul 25 22:05:13 0000cc8: f000 0000 .... Jul 25 22:05:14 0000ccc: f000 0000 .... Jul 25 22:05:16 0000cd0: f000 0000 .... Jul 25 22:05:18 0000cd4: 1800 0000 .... Jul 25 22:05:20 0000cd8: d800 0000 .... Jul 25 22:05:22 0000cdc: f000 0000 .... Jul 25 22:05:24 0000ce0: f000 0000 .... Jul 25 22:05:26 0000ce4: d300 0000 .... Jul 25 22:05:28 0000ce8: ec00 0000 .... Jul 25 22:05:30 0000cec: f000 0000 .... Jul 25 22:05:34 0000cf0: d300 0000 .... Jul 25 22:05:36 0000cf4: d000 0000 .... Jul 25 22:05:38 0000cf8: c100 0000 .... Jul 25 22:05:40 0000cfc: eb00 0000 .... Jul 25 22:05:42 0000d00: f000 0000 .... Jul 25 22:05:44 and that for the 2nd reference point was : Jul 25 22:05:46 0000068: d300 0000 .... Jul 25 22:05:48 000006c: d000 0000 .... Jul 25 22:05:50 0000070: ec00 0000 .... Jul 25 22:05:52 0000074: f000 0000 .... Jul 25 22:05:54 0000078: 1800 0000 .... Jul 25 22:05:56 000007c: d100 0000 .... Jul 25 22:05:58 0000080: c100 0000 .... Jul 25 22:06:00 0000084: dc00 0000 .... Jul 25 22:06:04 0000088: e000 0000 .... Jul 25 22:06:06 000008c: e000 0000 .... Jul 25 22:06:08 0000090: e000 0000 .... Jul 25 22:06:10 0000094: c300 0000 .... Jul 25 22:06:12 0000098: dc00 0000 .... Jul 25 22:06:14 000009c: e000 0000 .... Jul 25 22:06:16 00000a0: e000 0000 .... Jul 25 22:06:18 00000a4: e000 0000 .... Jul 25 22:06:20 00000a8: e000 0000 .... Jul 25 22:06:22 00000ac: e000 0000 .... Jul 25 22:06:24 00000b0: e000 0000 .... Jul 25 22:06:26 assuming fluctuations in the voltages ... I think the measurements are reasonable . Jul 25 22:06:28 isnt it ? Jul 25 22:06:30 m_w: Wormo_ nerdboy ds2 ^^ Jul 25 22:08:13 Can we now infer that the setup is working ? Jul 25 22:09:36 * nerdboy in a mtg and not following too closely... Jul 25 22:17:24 ZeekHuge: what voltage are you applying to the ADC input? Jul 25 22:19:21 sorry ZeekHuge demo day for my company Jul 25 22:19:36 Wormo_: no problem :) Jul 25 22:19:53 m_w: the second one is at about 0.37 Jul 25 22:20:17 but the values look mostly like e000 0000 Jul 25 22:20:27 in the second case Jul 25 22:20:46 ZeekHuge: try higher voltage Jul 25 22:21:08 its giving f0000000 Jul 25 22:21:16 let me check again .. Jul 25 22:46:12 ZeekHuge: those numbers look reasonable.... and you measure teh SHDN and /OE lines at the chip? Jul 25 22:46:40 n/m **** ENDING LOGGING AT Tue Jul 26 02:59:58 2016