**** BEGIN LOGGING AT Tue Oct 13 02:59:56 2009 Oct 13 06:48:35 hi, who asked about 4 bit ecc yesterday (afaik this channel is not logged, so can't read it back) Oct 13 06:54:10 eFfeM: hi, it was me Oct 13 07:07:06 dieter__, pm Oct 13 07:48:45 hi, anyone an idea on this? I moved from opensuse 11.1 to 11.2 the other day and now I do not get the jtag device any more; dmesg says: Oct 13 07:48:46 [ 3879.105067] usb 3-2: Ignoring serial port reserved for JTAG Oct 13 07:48:57 what am I missing/what should I add Oct 13 07:49:27 I do get /dev/ttyUSB0 as serial device (where it uses to be ttyUSB1 before upgrading where ttyUSB0 was for jtag Oct 13 07:55:29 i don't think you need to add anything Oct 13 07:55:40 my amontec dongle doesn't show up as ttyUSB* at all Oct 13 07:55:41 yet it works in openocd Oct 13 08:22:17 lennert: thanks, i never needed/used it but would like to avoid that i run into a problem later (e.g. if installing a new u-boot fails) Oct 13 08:44:55 anyone success in using the .32 git kernel with openrd client? Oct 13 08:45:32 i get an oops: Oct 13 08:45:34 Loading the saved-state of the serial devices... Oct 13 08:45:34 /dev/ttyS0 at 0x0000 (irq = 33) is a 16550A Oct 13 08:45:34 Unable to handle kernel paging request at virtual address 0cf0 Oct 13 08:47:16 btw it also seems serial on the .2.6.22.18 kernel has some issues, when I boot that one and use serial the system locks up after typing too many chars Oct 13 08:53:18 the loading the saved-state is from /etc/init.d/setserial Oct 13 09:00:44 apparently setserial or etc-setserial is the problem; did Oct 13 09:01:28 mv setserial setserial-; mv etc-setserial etc-setserial- Oct 13 09:01:28 and a reboot worked like a charm Oct 13 09:08:08 * eFfeM is trying to see if he can get openocd up and running with http://www.openplug.org/plugwiki/index.php/Setting_Up_OpenOCD_Under_Linux Oct 13 09:08:56 eFfeM: it's not exactly hard if you use debian (testing) or ubuntu. install the package and it works Oct 13 09:11:26 Md, i'm using opensuse .... Oct 13 09:11:36 the pacakge is not there Oct 13 09:12:11 but i have no problems compiling my own Oct 13 10:13:57 anyone netbooting freebsd on a sheeva ? Oct 13 10:18:44 hm, not making much progress on openocd, stuck at Error: unable to open ftdi device: device not found Oct 13 10:19:55 vid_pid is ok, but don't have a _desc, no idea if that is needed Oct 13 10:39:04 eFfeM: the included jtagkey.cfg doesn't work for you? Oct 13 10:39:17 or, what dongle are you using? Oct 13 11:07:08 lennert, i'm having an openrd client board which connects with a usb cable, i am using the openrd.cfg file Oct 13 11:07:20 (was afk for lunch :-) ) Oct 13 11:07:45 the openrd.cfg file from where? Oct 13 11:08:58 lennert: last thing I tried was the openocd client from the openrd page: http://code.google.com/p/openrd/downloads/detail?name=openrd_openocd.zip&can=2&q= Oct 13 11:09:05 this one had an openrd.cfg file Oct 13 11:09:26 made sure the interface had the proper vid/pid for the cable Oct 13 11:09:35 but guess it has to do with the absence of a device Oct 13 11:09:58 the config file already had the right vid/pid for your board? then you'd guess the config file would work Oct 13 11:10:00 when I insert the cable it says: Ignoring serial port reserved for JTAG Oct 13 11:10:05 eh, yeah, it's essential you have the board plugged in Oct 13 11:10:10 yes, there are 2 serial ports Oct 13 11:10:30 i only get one :-( which is the regular serial Oct 13 11:10:35 yes Oct 13 11:10:42 and the other one is not exported as a ttyUSB device Oct 13 11:10:58 it used to be in the past (with opensuse 11.1) Oct 13 11:10:59 openocd should attach to it regardless Oct 13 11:12:15 plugwiki http://www.openplug.org/plugwiki/index.php/Setting_Up_OpenOCD_Under_Linux#Getting_OpenOCD_For_The_SheevaPlug says: Oct 13 11:12:16 Note that the /usr/local/lib/openocd/board/sheevaplug.cfg might be missing a configuration directive. If openocd complains add the following line to the sheevaplug.cfg file: ft2232_device_desc "USB <-> Serial Cable A" Oct 13 11:12:38 since I was missing the _desc file as well in openrd.cfg I added that one as well Oct 13 11:12:41 but to no avail Oct 13 11:13:09 what's the output of lsusb ? Oct 13 11:13:24 Bus 003 Device 014: ID 0403:9e90 Future Technology Devices International, Ltd Oct 13 11:13:43 and the cfg file says Oct 13 11:13:43 Bus 003 Device 014: ID 0403:9e90 Future Technology Devices International, Ltd Oct 13 11:13:44 strange that you don't have a root hub Oct 13 11:13:58 oh yes, i only copied the ftdi line Oct 13 11:14:04 oh, ok Oct 13 11:14:11 cfg file contains: ft2232_vid_pid 0x0403 0x9e90 Oct 13 11:15:31 hm Oct 13 11:19:04 i didn't have a _desc line so I added to target/interface/openrd.cfg the line Oct 13 11:19:05 ft2232_device_desc "USB <-> Serial Cable A" Oct 13 11:20:42 no idea whether that should be ok, but that is what plugwiki gave Oct 13 11:22:36 git head sources suggest that you need to specify either a device desc or a serial Oct 13 11:22:44 and if you don't give one of those, it can't open the device Oct 13 11:22:48 so it does appear to matter Oct 13 11:23:11 i added the device desc (as found on plugwiki) but no idea how to verify that it is ok Oct 13 11:26:11 apparently in the more recent ftdi_sio the jtag port is skipped Oct 13 11:27:33 hm, dmesg says: Oct 13 11:27:34 Product: OpenRD JTAGKey FT2232D B Oct 13 11:27:43 should that be in device desc ? Oct 13 11:28:27 sheeva has something like taht, will give it a try Oct 13 11:30:31 yeah, try that Oct 13 11:30:35 that ought to work better Oct 13 11:34:16 no effect :-( Oct 13 11:34:30 try with -A at the end? Oct 13 11:35:00 no effect either Oct 13 11:40:00 hey guys :) Oct 13 11:40:13 I shown the sheeva at a linux meeting, I think most of them are going to get one lol :) Oct 13 11:42:44 dah, found it Oct 13 11:43:01 eFfeM: what was it? Oct 13 11:43:08 one sec Oct 13 11:46:53 lennert i used the openocd from the bin package I mentioned above Oct 13 11:47:02 just decided to verify its version Oct 13 11:47:05 file said: Oct 13 11:47:05 openocd: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked, for GNU/Linux 2.2.5, not stripped Oct 13 11:47:15 for 2.2.5 ! Oct 13 11:47:19 when you compiled openocd yourself, did you enable the ftdi support? :) Oct 13 11:47:33 2.2.5 just means the compat version, your binaries will probably have the same Oct 13 11:47:52 so now moved to the openocd head (with ftdi support) and ran that with the cfg file and it works Oct 13 11:48:10 apparently the prebuilt binary cannot deal with _desc or so Oct 13 11:48:15 didn't really check the sources Oct 13 11:48:26 but I can now confirm it works Oct 13 11:48:56 need to go to office now, will try to write something up tomorrow (or this evening if the students are quiet :-) (idle hope :-) ) Oct 13 11:49:30 lennert: thanks alot for your suggestions Oct 13 12:42:21 hum, i've got an interesting problem netbooting freebsd... for some reason the kernel loads init with "-s" (single user) Oct 13 12:43:42 and i have no idea why that is, since normally one chooses single user from the boot loader, and obviously uboot is doing the loading work here Oct 13 14:20:07 lool: did the openocd stuff I gave you for openrd actually make it to upstream? Oct 13 14:26:56 ron__: I dont think so, no Oct 13 14:27:20 ron__: I think they committed my sheeva patch, and closed the bug tracker where I had filed it Oct 13 14:27:29 They moved to another bug tracker IIUC but I dont know where Oct 13 14:31:46 lool: hmm ok. I haven't had any (other) reason to be in touch with them myself, but it would be nice to get that merged Oct 13 14:33:29 I agree Oct 13 18:36:43 <_dieter_> eFfeM: just for interest: do you know why setserial crashes your system? Oct 13 18:36:58 <_dieter_> eFfeM: or do you have a wrong / buggy setserial version? Oct 13 18:44:54 dieter__: i've no real idea. the setserial works with the 2.6.22.18 kernel. Then again I seem to recall something in the openrd client notes that serial was also not finished; guess my problem is due to that. Oct 13 18:45:22 * eFfeM actually has not too much of an idea what setserial does, never used it, not done anything with serial on openrd Oct 13 18:50:18 <_dieter_> eFfeM: I would expect that the serial port of openrd would be the same than eg on sheevaplug. Oct 13 18:50:51 <_dieter_> So hopefully the kernel shouldn't cause such a behaviour? Oct 13 19:02:03 dieter__: i'm not too sure about driver etc Oct 13 19:03:24 the todo says sd/uart1 selection Oct 13 19:03:52 could be setserial is trying to restore thngs and the driver is not that good, didn't really dig into it Oct 13 19:05:05 <_dieter_> eFfeM: maybe it tries to enable uart1? hm, haven't ever seen some issues with serial on kirkwood boards. Oct 13 19:07:18 guess so, didn't study the oops or stack backtrace enough Oct 13 19:09:10 <_dieter_> eFfeM: ok - we will see it, if not ;) Oct 13 19:13:31 dieter__: the log seems to suggest /dev/ttyS0 Oct 13 19:14:05 not fully sure though Oct 13 19:14:19 see my post with the oops on the mailing list. Oct 13 19:14:53 if someone with more knowledge than me can coin a test I'll be more than happy to do it tomorrow (now about 30 km away from the board) Oct 13 19:17:20 anyone any experience connecting a phone to openrd client? Oct 13 19:24:55 lol Oct 13 19:24:57 eFfeM: how? Oct 13 19:26:39 <_dieter_> eFfeM: what kind of phone do you want to connect? Oct 13 19:30:19 an analog phone, there is a TDM header and the telephony driver so I assumed that this is for a "classic" phone Oct 13 19:30:20 or am i totally wrong? Oct 13 19:30:39 the board then could function as ATA Oct 13 19:30:39 only half wrong :) Oct 13 19:30:42 <_dieter_> eFfeM: yes - you're right. Marvell has also an reference design for exactly what you want. Oct 13 19:30:45 there is no SLIC Oct 13 19:31:16 ah ok, thanks for the info Oct 13 19:31:22 that part of the doc was somewhat confusing Oct 13 19:31:33 <_dieter_> eFfeM: do you have access to marvells extranet? Oct 13 19:33:08 does the -client have a PCI connector? you could put an analogue telephony card in it ;) Oct 13 19:34:05 dieter__: i think i have access to the extranet Oct 13 19:34:25 ron__: client does not have a pci connector, pci is used for vga, base has a pci connector Oct 13 19:34:40 no real need for telephony, just exploring what I could do with it Oct 13 19:35:12 will use sip telephony if required (i have a small usb handset with kbd, only disadvantage is that is is wired) Oct 13 19:35:15 <_dieter_> from rd_88F6281 docu: Oct 13 19:35:24 with ATA one can connect a dect handset Oct 13 19:35:34 ah yep. I didn't recall seeing a hole in the pictures of the enclosure :) I've only got base boards here Oct 13 19:35:34 only eur 11 at mediamarkt Oct 13 19:36:12 <_dieter_> TDM and SPI interfaces are connected to Si3215 ProSLIC devices and an Si3050 (DAA) device. Oct 13 19:36:26 need to go, thanks for the info Oct 13 19:36:31 cya tomorrow Oct 13 19:36:36 <_dieter_> bye! Oct 13 19:37:57 <_dieter_> ron__: do you now if there is somewhere a driver for the SPI interface inside the TDM module for git kernel available? Oct 13 19:39:00 I don't think so, only for the other SPI interface ... Oct 13 19:39:45 but it wouldn't be rocket science to wire it up, the SPI core is pretty sane, so it's just joining that to the peripheral registers mostly Oct 13 19:39:46 <_dieter_> for the stock 2.6.22 kernel there is a driver but not for git kernels up to now :( Oct 13 19:41:00 yeah, there's a whole bunch of stuff missing. I should have some ready to push soon Oct 13 19:41:03 <_dieter_> yes - but if there is one in the wild... Oct 13 19:41:23 <_dieter_> what kind of stuff you're working on? Oct 13 19:41:55 some of what's in the LSP is pretty 'wild' yeah :) Oct 13 19:42:17 <_dieter_> uuuhhh, so it looks like you have much to do :) Oct 13 19:43:00 I need to mess with SPI tomorrow, but the other one, not the one you're looking at. Oct 13 19:43:25 I've got a driver for the TS peripheral pretty much ready to push now Oct 13 19:43:59 <_dieter_> IMHO the "common" spi driver is pretty useless - at least for openrd / sheevaplug due to the pin muxing? Oct 13 19:44:27 <_dieter_> Ah, do you work on some video application? Oct 13 19:44:46 yes, that's why I'm booting from sata, I had to steal those pins back from the nand :) Oct 13 19:45:17 <_dieter_> you're lucky - I have to run embedded from flash :( Oct 13 19:45:41 but we really are just using this board for prototyping, so there is fresh solder and extra wires all over the place ... Oct 13 19:46:17 <_dieter_> me too - but if you need nand there are not so many ways to do this... Oct 13 19:50:57 yeah, the nand will go back on our board run, but we can use other pins for the spi then Oct 13 19:51:57 <_dieter_> maybe next week I will try to port the SPI stuff to TDM module. Oct 13 19:54:26 I probably wouldn't bother trying to 'port' that. just have a look at the SPI subsystem in current kernels, there's only a couple of things you need to wire to the right registers, and it's pretty well documented as things in lk go Oct 13 19:55:40 * _dieter_ will have a look and comes back if there are questions ;) Oct 13 19:56:11 * ron_ should get some sleep in the meantime, but I'll be around later :) Oct 13 19:58:03 <_dieter_> ron_: have a good night! Bye! Was nice to have a small talk ;) Oct 13 21:33:07 the kernel says one of my serial deviecs is jtag Oct 13 21:33:11 but i dont think it has the right one Oct 13 21:33:15 theres nothing showing up on console Oct 13 21:33:27 i dont know what to do, except to go reinstall some old kernel & try again **** ENDING LOGGING AT Wed Oct 14 02:59:56 2009