Tuesday, 2014-06-24

*** tpb has joined #timvideos00:00
tijashenki: I was trying to install your driver for usb uart. sudo make install gives an error.00:08
tijamake: *** No rule to make target `install'.  Stop.00:08
*** xfxf has quit IRC00:45
*** xfxf has joined #timvideos00:57
mithroayush3504: I'll be around in 30->45 minutes01:05
mithroshenki: are you on the fpgalink list?01:55
mithroayush3504: opps, lunch time. Will be back in an hour.02:10
shenkitija: okay. we probably shouldn't make install it anyway, as it conflicts with the cdc-driver02:23
shenkitija: you need to follow the steps in the README.exar02:24
shenkitija: rmmod cdc_acm && rmmod vizzini && modprobe -r usbserial && modprobe usbserial && insmod ./vizzini.ko02:24
shenkiim not sure how necessary all of those steps are02:25
shenkiwe really should get support for the device upstream02:25
shenkibut that's not a concern for you at this stage02:25
ayush3504mithro: no prob :)02:32
tijashenki: okay, will do that02:37
shenkitija: hows the progress?02:38
tijashenki: I was planning to use fpgalink library to bring debug data from fpga to pc02:38
tijaturns out that since fx2 is already being used, it will be difficult. And I don't want to mux pins as I don't want to disturb the stream02:39
tijaotherwise it would have been really elegant way to send data from fpga.02:40
tijaNow I am planning to use the UART02:40
shenkimithro: no, im not on the fpgalink list02:41
shenkitija: we already have a serial pipe from the fx2 to the PC02:41
shenkitija: when you load our firmwrae on the fx2, you will notice it exposes a USB CDC-ACM device02:42
tijashenki: but isn't it using pins for video streaming02:42
tijashenki: I mean can I send serial data without affecting the video stream02:43
shenkitija: yes02:43
shenkiyou can02:43
tijashenki: oh okay! then i guess I need to figure that out. I don't have much knowledge about fx2 part of hdmi2usb firmware.02:45
mithroayush3504: back now02:46
mithroayush3504: just going through your responses to the github issues02:47
mithroayush3504: then I wanted to chat about auto-detection02:47
shenkitija: yeah. whichever one works for you02:47
shenkitija: the advantage of that one is we already have some infrastructure set up02:48
shenkitija: but it's upto you; if you want to use the xr21v141x one that you've got going, then that's good too02:48
shenkiwhichever you find easier02:48
tijashenki: fine02:53
mithroayush3504: can you give me edit permission to your repo so I can reopen the issues I need to?02:59
shenkitija: how are you going with the desgin document?03:18
tijashenki: I am planning to use switched to select which debug data should be sent serially. So first I am deciding what are the relevant debug data.03:29
tijashenki: But before that I need to decide which serial interface I am going to use. I am reading the code of cdc in fpga firmware. Actually that is being used to send commands to encoder and image selector.03:31
mithrotija: that is *part* of the design document03:31
mithrotija: IE it should include the things you looked at and why you chose to select the bits you did03:31
mithroayush3504: poke?03:31
shenkitija: as mithro said, we need to get into a good habbit of specifying what we're going to do before we start hacking03:34
shenkitija: so before reading the code, write down what the problem is, how you plan to solve it given what you currently know03:35
shenkitija: then we can help you by filling in the blanks03:35
shenkiit's okay if you then start reading the code and realise you need to change the design03:35
shenkiit's not a formal report or anything, just some notes in a google doc03:35
shenkitija: take this one for example: https://docs.google.com/document/d/1-E4SGuPz4Wjqs2BP9ck8GL6wrxWUUAnE6lsq7E3uBgE/edit03:36
tpbTitle: I2C VHDL Cores & their comparison - Google Docs (at docs.google.com)03:36
tijashenki: okay I got it! My laptop battery is going to die (No power here). I will make a design doc asap.03:40
shenkitija: okay03:41
shenkitija: you made a commitment to get this debug stuff done by end of wednesday. do we need to revisit that deadline?03:41
tijashenki: No, I  will put some extra hours and try to complete by then. Only thing is the exar driver should work which I will test once power is back.03:44
shenkitija: okay03:44
shenkitija: can you tell me more about the power situation?03:44
tijashenki: It goes off in the morning so I  sleep then. Comes back in the afternoon so I wake up have my lunch and then start working.03:46
shenkitija: it interests me, as i've not lived somewhere where i've had to deal with that03:48
shenkitija: how do you get net connectivity?03:48
ayush3504mithro: in a while, no power...03:50
tijashenki: USB powered broadband modem. I am planning to go back to my parent's place and work from there.03:51
*** tija has quit IRC03:54
ayush3504didn't notice that a discussion on power cuts is already going on :p04:06
ayush3504mithro: back04:06
mithroayush3504: great04:06
mithrostill going through my email04:06
ayush3504mithro: ok04:07
mithroayush3504: so about auto-detection04:29
ayush3504mithro: yes, did u understand what I did for auto-detection?04:29
mithroayush3504: it looks like you are currently planning for every daughterboard to have EEPROM or microcontroller on it to identify them?04:29
ayush3504mithro: yes, every daughterboard can have a cheap pin addressable eeprom04:30
ayush3504mithro: costs some $0.204:30
mithroayush3504: when saying prices you should always do it in $X.XX, ie $0.2004:31
mithroayush3504: I misread that as $0.02 at first04:31
ayush3504mithro: $0.24 for 10004:32
ayush3504mithro: $0.31 for 104:32
mithroayush3504: I was thinking that we could instead have a very small micro-controller on the motherboard which reads the RC identity values from daughterboards and presents the info via the I2C interface (effectively emulating the EEPROM)04:33
ayush3504mithro: yes that's what i was initially doing04:33
ayush3504mithro: the cost of micro is comparable to cost of 6 eeproms04:34
ayush3504mithro: and it's much more complex04:34
ayush3504mithro: the eeprom method is simple and can also store more data about the daughterboard04:35
ayush3504mithro: that ID controller sheet you mentioned was using the microcontroller for RC detection, and emulating itself as an eeprom on I2C.04:35
shenkisimple is good04:35
ayush3504thanks shenki :)04:36
mithroayush3504: what type of micro where you looking at btw?04:40
ayush3504mithro: PIC16F1704 the 2nd cheapest micro i found on parametric search with i2c and sufficient pins.04:41
ayush3504mithro: here's how the eeprom method would work - the atlys would poll on i2c on slave address 0 eeprom which contain ID and possibly some more data about the expansion board connected. If the ID is found to be of serial expansion board, it would read from slave address 1,2,3...7 to get ID strings from daughterboards.04:42
shenkiyou don't need an i2c periperhal; you can bitbang i2c04:46
ayush3504shenki: true, I wanted to use the same micro for other things. Like this micro has a UART which makes it useful for me to use in daughterboards.04:53
shenkiayush3504: sounds good04:54
ayush3504mithro / shenki: RC detection seems to have another issue that it relies on logic level thresholds of the I/O pins. A slight error in that  will change the measurements greatly. How much will it change is not known because the errors in logic level thresholds are not given in datasheet. It can slightly vary depending on temperature, VCC, noise and production05:01
ayush3504batch. A comparator with precision reference could be used, but then it makes things even more complex.05:01
mithrosorry, got called into quick meeting05:05
mithroback now05:06
mithroayush3504: this is another case where I would recommend having a spreadsheet which shows the information comparing the cost of the two solutions05:06
shenkii don't like the idea of RC detectio05:09
shenkii don't like the idea of RC detection05:09
shenkifor the reasons you mention ayush350405:09
shenkii mean, we should easily be able to do a few different levels05:10
shenkibut are we really that short on pins? couldn't we use resistors to encode a number on a few pins?05:10
mithroshenki: you should point ajit to Rohit's blog and this post in particular -> http://dreamsxtrinsic.blogspot.com.au/2014/06/gsoc-daily-log-trails-errors-part-2.html05:12
tpbTitle: [GSoC Daily Log]: Trails & errors - Part 2 | Dreams eXtrinsic (at dreamsxtrinsic.blogspot.com.au)05:12
shenkimithro: ok05:13
mithroRC detection is only a good solution if it's much cheaper than an EEPROM solution - It should be 5c compared to 35c to make it worth doing.05:14
mithrodoes I2C allow "chaining / passthrough" like SPI? Its normally configured as multi-tap bus style....05:23
mithroayush3504: ping?05:23
ayush3504mithro: yes05:24
ayush3504mithro: simply connecting them in parallel works05:24
mithroayush3504: but that requires them to all have unique addresses, right?05:24
ayush3504mithro: yes, those are given by address pins A0, A1, A205:24
mithroayush3504: if we where using SPI you'd just attach them all serially and then just keep reading information until you got an empty byte, thus auto-detecting the number of devices attached05:25
ayush3504mithro: yeah, but daisy chaining has a problem, for example if you remove one of the SPI device in the chain, it breaks it.05:28
mithroayush3504: sure, it means you need to populate the slots in an increasing order or have a jumper which shorts the SDI/SDO pins around the missing chip05:29
ayush3504mithro: yeah, i2c is better in that regard05:29
mithroayush3504: I still think we don't have the right solution for the serial board / auto-detect yet05:34
ayush3504mithro: RC is not suitable for the technical reasons i gave05:34
mithroayush3504: yeah, I'm leaning towards an I2C based solution - the question is how to make that work05:35
ayush3504mithro: did you not clearly understand the i2c eeprom method?05:36
mithroayush3504: no, I understand it - each daughterboard has an i2c eeprom who's address is set via the slot it is plugged into05:37
ayush3504mithro: exactly05:37
mithroayush3504: the motherboard has a i2c eeprom too05:38
ayush3504mithro: yes05:38
mithroayush3504: having the FPGA scan the serial motherboard and then the daughterboards seems not the best05:39
ayush3504mithro: the fpga logic will read expansion board ID on slave address 0. It wouldn't read higher slave addresses unless it finds a serial expansion board.05:39
mithroayush3504: I'm wondering if the motherboard could end up being totally passive and we could just scan for the daughter boards directly05:39
ayush3504mithro: or any other board that's modular in nature05:40
mithroayush3504: yeah05:40
mithroayush3504: for example, if we ended up with two expansion boards which didn't use all the pins then we could have a VHDCI splitter or something05:41
ayush3504mithro: hmm, yes. technically it's not necessary to have eeprom on motherboard if the FPGA is made to handle exceptions when it doesn't find eeprom on a particular slave address.05:42
mithroayush3504: I'm trying to figure out how we could change the auto-detection method to allow multiple daughterboards05:43
mithroayush3504: s/daughterboards/VHDCI expansion boards/05:43
mithroayush3504: then your motherboard could just end up as VHDCI -> PMOD converter05:44
ayush3504mithro: i think it's straight forward. It would depend on what ID it reads on slave 0. Let's reserve slave 0 to contain data only about the expansion board. If it doesn't read anything on slave 0, it would scan higher addresses to find possible daughterboards. This can also work if a another expansion board and two daughterboards are connected using the05:46
ayush3504splitter idea.05:46
mithroayush3504: that requires the splitter to be more than just wires (it needs to shift one of the daughterboards to another address)05:47
ayush3504mithro: well first let's not make it a condition to read higher addresses depending on ID on slave 0, second, we won't populate slave 0 eeprom on motherboard. So it doesn't require changing any addresses05:48
ayush3504mithro: for this top work the daughterboard addresses should always start from 105:49
mithroayush3504: I was thinking that each expansion board used a different address, and we just scan the i2c bus for devices05:50
ayush3504mithro: yes, the address could however start from 1. 0 can be reserved from expansion board ID05:52
mithrosadly it doesn't look like i2c ever thought about multiple devices at the same address05:52
ayush3504mithro: also think about the case, if you were to include daugherboard circuits on the PCB, i.e. a customized pre-loaded. in such case you would want to use only one eeprom at address 0.05:53
ayush3504mithro: technically we can have multiple slave devices at same address only if they listened to the bus, but that's not very useful in our case.05:55
mithroayush3504: yeah05:58
mithroayush3504: what EEPROM are you proposing to use?05:58
mithroayush3504: still waiting on your weekly progress report too05:58
ayush3504mithro: 24AA01405:58
ayush3504mithro: http://in.mouser.com/ProductDetail/Microchip-Technology/24AA014-I-SN/?qs=gySgac5WNsHB6VrGKNil7A==05:58
tpbTitle: 24AA014-I/SN Microchip Technology | Mouser (at in.mouser.com)05:58
mithroOh, is there a standard for EEPROM I2C interface?05:59
ayush3504mithro:  I think so, because there's a standard library to talk to 24xx eeproms in arduino.06:00
mithro24xx EEPROMs are only one type of EEPROM - 24xx is probably a family of EEPROMs right?06:01
mithro24xx might be "standard" enough though....06:04
ayush3504mithro: yes a family06:04
mithroayush3504: it looks like that EEPROM is 1kbit? IE 128 bytes?06:05
ayush3504mithro: yes. I found this to be the cheapest one in parametric search with cascading support (pin adressing)06:05
mithroWe decided on I2C because rohit doesn't have any spare pins right?06:07
*** CarlFK has joined #timvideos06:11
*** ChanServ sets mode: +v CarlFK06:11
mithrowb CarlFK, I'm guessing your probably asleep?06:20
mithroayush3504: where did you do the parametric search?06:20
CarlFKmithro: I will be soon - spent the day trying to setup a site for presenters to edit their talk video metadata, and nothing went right, and rushed out the door before I could get to calling up Fedx06:22
ayush3504mithro: http://www.microchip.com/ParamChartSearch/chart.aspx?branchID=70002&mid=&lang=en06:23
tpbTitle: 24xx01 Products - Microchip Technology Inc (at www.microchip.com)06:23
mithroayush3504: Using Microchip's parametric search is only going to give you microchip's solutions06:23
ayush3504mithro: $0.19 here06:23
mithroayush3504: can you try at something like Mouser or Digikey?06:24
ayush3504mithro: tried that first. found the parametric search crappy. i'll try again06:25
mithroayush3504: yeah - maybe just use it to find out alternative's to microchip and search on their sites directly06:26
mithroayush3504: how are you going updating your requirements document?06:27
ayush3504mithro: Yes there's a lot of updating there to do. I only have to add things that we have discussed and agreed upon.But I should do it a bit later, because there are other the pending tasks - like getting the PCB done06:29
*** slomo has joined #timvideos06:30
ayush3504mithro: in mouser parametric search, the cheapest 8 pin eeproms are from microchip. Anything less than 8 pins (like SOT-5) will not have address pins.06:36
mithroshenki / Joelw / anyone else with an opinion. If the HDMI2USB device had an embedded processor inside it - what architecture should it be? http://opencores.org/usercontent,doc,1393289758 seems to be a good summary of the options.06:54
*** rohitksingh has joined #timvideos06:54
shenkimithro: inside the fpga?06:55
mithroshenki: yeah06:55
mithroheyo rohitksingh06:55
rohitksinghmithro: hi :)06:56
shenkiprobably some variant of the leon06:56
shenkidepends what we wanted it to do06:57
shenkimicroblaze would work fine too06:57
techman83What is the Leon doing?06:57
techman83me = Leon :P06:57
shenkimithro: ^06:57
mithroshenki: PicoBlaze might be a solution too06:57
shenkii got the impression that needed to be coded in asm06:58
shenki(the code that runs on it needs to be)06:58
mithroshenki: for doing things like managing the "control" of the system (such as reading from the control serial port, responding with information, probing and configuring the expansion board and other peripherals, etc)06:58
shenkii'd go with the microblaze06:59
mithroshenki: PicoBlaze is not well suited to C style code06:59
rohitksinghmithro: referring the logs, yes, the I2C was mainly decided due to lack of any extra pins06:59
shenkithe downside is it's xilinx specific06:59
mithroshenki: there are open implimentations of it from what I can see06:59
mithrodon't know how good / compatible they are06:59
mithroUsing something like PIC / AVR / 8052 would mean we have better compiler support but more of an impedance mismatch with FPGA (hence possible more LUT usage?)07:00
shenkiupside is that it's easy to use, and i have experience with it07:00
shenkian external PIC/AVR/8051?07:01
tpbTitle: Andreas playing Mario on a Gameboy emulator running on 4 Microblaze CPUs - YouTube (at www.youtube.com)07:01
shenkior you mean a soft one?07:02
shenkiif we were going to put a core on there, you'd want it to be something that's easy to program07:02
shenkiotherwise why are you using a core instead of coding HDL07:03
mithroshenki: soft one07:03
shenkiso that would mean something where you can go apt-get install foo-bar-gcc && make && make run07:03
mithroshenki: AVR/8051/PIC all have support via tools like sdcc07:03
mithroayush3504 / rohitksingh: meeting?07:03
shenkiyeah, that's what i mean07:03
shenkiyou want to be able to just use gcc07:03
shenkiavr is supported by gcc07:03
ayush3504mithro: i'm ready07:03
rohitksinghmithro: ready07:04
mithroI'm not seeing anyone else in the call?07:04
ayush3504mithro: says "This party is over..." on mine07:04
aps-sidsslomo: hi, what could be the reason for this error? gstbasesrc.c(2865): gst_base_src_loop (): /GstPipeline:pipeline-overlay-video/GstBin:bin0/GstAppSrc:source: streaming task paused, reason not-negotiated (-4).  Whole debug log is located here - http://paste.ubuntu.com/7693402/  error occurs around line 120007:32
tpbTitle: Ubuntu Pastebin (at paste.ubuntu.com)07:32
slomoaps-sids: segment event before caps, segment having the wrong format... and it looks like the caps are also rejected by your set_caps() function or something07:39
slomoaps-sids: what's the pipeline? are there custom elements in there?07:39
aps-sidsslomo: I don't think there are any custom elements. Pipeline should be there in the log.07:41
slomoaps-sids: can you extract it from the log for me? :)07:42
aps-sidsslomo: also, segment before caps warning is there for other components but they still work fine. I was more concerned about the critical errors.07:43
aps-sidsslomo: just a min. I'm on mobile07:43
slomoaps-sids: the caps in there are not valid 1.x caps in any case07:44
slomothere is no bpp, depth, *_mask anymore07:44
slomoit's just video/x-raw,format=somestring07:45
slomothat might be the reason why the caps are rejected07:45
slomoif you get me a log with GST_DEBUG=6 (not 5 as that one), i can probably tell you more07:45
slomobut also the event misordering that happens there is worrying07:45
*** rohitksingh has quit IRC08:14
aps-sidsslomo: I removed bpp, depth, *_mask, still the error. Here's the DEBUG=6 log -- http://s000.tinyupload.com/download.php?file_id=00971454773040291985&t=009714547730402919852681108:22
tpbTitle: TinyUpload.com - best file hosting solution, with no limits, totaly free (at s000.tinyupload.com)08:22
aps-sidsthanks for helping :)08:22
*** rohitksingh has joined #timvideos08:28
slomoaps-sids: try removing endianess too ;)08:33
slomoaps-sids: and then a new log08:33
slomoaps-sids: see line 37220 and the few lines above08:33
aps-sidsslomo: still error, uploading new file08:40
aps-sidsslomo: http://s000.tinyupload.com/?file_id=5452526276568412969608:42
tpbTitle: TinyUpload.com - best file hosting solution, with no limits, totaly free (at s000.tinyupload.com)08:42
slomoaps-sids: video/x-raw, width=(int)320, height=(int)240, framerate=(fraction)0/1 in anything we support08:44
slomoallowed caps video/x-raw, width=(int)320, height=(int)240, framerate=(fraction)0/1, format=(string)AYUV, pixel-aspect-ratio=(fraction)1/1, interlace-mode=(string)progressive, colorimetry=(string)bt601; video/x-raw, width=(int)320, height=(int)240, framerate=(fraction)0/1, pixel-aspect-ratio=(fraction)1/1, interlace-mode=(string)progressive, format=(string){ RGBA, BGRA, ARGB, ABGR, AYUV }08:44
slomotry adding interlace-mode=progressive there08:49
slomobut quite curious that it's required in all cases08:49
slomoit should only for the conversion cases08:49
aps-sidsslomo: this is actually a conversion case, an overlay component08:50
slomowhy are you using alphacolor btw?08:51
aps-sidsslomo: i am not really sure since i am porting from gst-0.10 where it was used.08:53
aps-sidsslomo: format option is not there in pipeline. Should it be there?08:53
slomoaps-sids: try replacing alphacolor with videoconvert :)08:53
aps-sidsslomo: oh,i has replaced ffmpegcolorspace with video convert as well.08:56
slomoyeah, ffmpegcolorspace is gone and videoconvert does the same08:57
slomobut alphacolor is mostly useless, was already in 0.1008:57
aps-sidsslomo: still no luck09:01
slomohow does it fail with videoconvert?09:03
*** rohitksingh has quit IRC09:03
aps-sidsslomo: same error09:03
aps-sidsslomo: should i send a new log?09:04
aps-sidsslomo: and should format option be there in pipeline? (I've tried both with and without)09:06
slomodepends on what you want to do there09:06
slomoi still don't know the pipeline and what problem it's trying to solve at that part ;)09:07
aps-sidsslomo: http://s000.tinyupload.com/index.php?file_id=8329719049316689603709:11
tpbTitle: TinyUpload.com - best file hosting solution, with no limits, totaly free (at s000.tinyupload.com)09:11
slomoaps-sids: ok09:15
slomoaps-sids: where do these caps even come from?09:15
slomovideo/x-raw, width=(int)320, height=(int)240, framerate=(fraction)0/1, interlace-mode=(string)progressive09:16
slomoi mean09:16
aps-sidsslomo: This is a CAPS_TEMPLATE in the code. just wait, I'm pushing the code changes to repo.09:16
slomoaps-sids: and that's the caps on a source element?09:17
aps-sidsslomo: I've ported Pango and PangoCairo and there might be some other problems09:17
aps-sidsyes, source element09:18
aps-sidsslomo: here's the commit https://github.com/aps-sids/flumotion-orig/commit/9b7c88c682cc62138a8b2dd465ef6014a89fa33e09:24
tpbTitle: Ported Overlay component · 9b7c88c · aps-sids/flumotion-orig · GitHub (at github.com)09:24
slomoaps-sids: ok, so you have a custom source element09:29
slomoand you don't provide complete caps in it09:29
slomofields are missing09:30
slomoespecially format=BGRA (test if that works, otherwise it's ARGB ;) )09:31
slomoand pixel-aspect-ratio=(fraction)1/109:31
slomoif you use the API from libgstvideo you wouldn't have to worry about that09:31
aps-sidsokay. I should add these to CAPS_TEMPLATE right?09:32
slomoor you just use the GstVideoInfo API to create the caps for you09:34
slomoinstead of doing stuff with strings09:34
aps-sidsslomo: nstreaming task paused, reason not-negotiated (-4) is gone09:35
aps-sidsGStreamer-CRITICAL **: gst_segment_to_running_time: assertion `segment->format == format' failed     is still there09:35
slomoyes and also the event misordering is still there09:36
aps-sidshow to go about that?09:36
slomowhen do you set the caps on the srcpad?09:36
slomoand are you configuring a time segment?09:36
slomobasically you just have to implement GstBaseSrc::get_caps() and return your caps there09:45
slomoand call gst_base_src_set_format() with GST_FORMAT_TIME during initialization09:45
slomoand after that not worry about caps or segments or any other events09:45
*** rohitksingh has joined #timvideos11:35
*** FeltonChris has quit IRC11:47
*** tija has joined #timvideos16:53
*** rohitksingh has quit IRC17:34
*** rohitksingh has joined #timvideos17:34
*** CarlFK has quit IRC18:23
tijarohitksingh: any issuse with the UART?18:25
rohitksinghtija: not yet...working wonderful in windows...for past two days I haven't ran my board...will do today...but no issues as of now! :) and thanks for the code!18:27
tijarohitksingh: you mentioned in your blog you had to regenerate the core?18:27
rohitksinghtija: no i removed the core...because i already had 50MHz clock present :)18:28
rohitksinghtija: maybe i should look what i may have written in the blog inadvertently18:29
tijarohitksingh: okay! Did you try it in linux? Btw shenki has updated the drivers for newer kernel.18:30
tijathe code is available in his git repo18:31
rohitksinghtija: great! will try it tonight!18:32
*** CarlFK has joined #timvideos18:41
*** ChanServ sets mode: +v CarlFK18:41
*** rohitksingh has quit IRC18:41
*** slomo_ has joined #timvideos18:41
*** tija has quit IRC18:43
*** slomo has quit IRC18:43
*** rohitksingh has joined #timvideos18:49
*** slomo has joined #timvideos20:03
*** slomo has joined #timvideos20:03
*** slomo_ has quit IRC20:04
*** tija has joined #timvideos21:22
tijarohitksingh: Did you test the linux driver?21:31
*** CarlFK has quit IRC21:31
rohitksinghtija: will do in just few more minutes...21:33
*** CarlFK has joined #timvideos21:34
*** ChanServ sets mode: +v CarlFK21:34
tijarohitksingh: I am having some problems. If it works let me know.21:34
rohitksinghtija: sure!21:35
*** puck has joined #timvideos21:41
rohitksinghtija: can't get any output...devices comes up as ttyUSB0 and dmesg also reports fine21:54
tijarohitksingh:same here21:55
rohitksinghtija: inserting vizzini module blocks my beaglebone black's usb-serial from working too22:26
rohitksinghtija: actually removing the vizzini module...the Exar one enumerates as ttyACMx and is working fine22:28
tijarohitksingh: what is working to fpga uart or the beagle bone22:29
rohitksinghtija: both...beaglebone shows up at ttyACM0 and FPGA's uab-serial as ttyACM1 and i can see my project's debug output. BTW which client do you use for hex output from serial?22:31
rohitksinghtija: ^ that is after removing the vizzini module22:32
tijarohitksingh: okay will do that. btw I am use gtkterm22:32
rohitksinghtija: ah! got it! gtkterm has hexadecimal view options from "View" menu..thanks...now i can see proper values! :) previously i was using cutecom, but it wasn't good22:36
tijarohitksingh: good going! let me get my thing working.22:38
rohitksinghtija: great!22:38
tijarohitksingh: btw why do you need a beagle bone?22:42
rohitksinghtija: for rapid prototyping of AD9984A I2C initialization, and to view its status registers for debugging using I2C22:43
aps-sidsmithro: please ping when you have 2 minutes22:53
*** sarwarc has joined #timvideos23:32
*** rohitksingh has quit IRC23:35
*** sarwarc has quit IRC23:41
*** rohitksingh has joined #timvideos23:55

Generated by irclog2html.py 2.12.1 by Marius Gedminas - find it at mg.pov.lt!