2011-01-03 01:18 Hi! Quick question... I had a LOVE program crash and lock the SDL screen. 2011-01-03 01:18 All black, nothing showing. I'm still logged in through ssh but I don't see any process 2011-01-03 01:18 to kill and get my framebuffer back. What should I do? Thanks! 2011-01-03 01:18 BTW, this is for the NanoNote... 2011-01-03 01:51 oofoe: seems that you'll have to await the return of the maker of love ... (or just reboot :) 2011-01-03 01:57 I think he's asleep... ; - ) 2011-01-03 01:57 I just thought someone else might have run into the problem another way. 2011-01-03 01:57 However! 2011-01-03 01:57 I have learned how to turn off the LCD backlight from the shell... 2011-01-03 01:58 You can echo a "1" into /sys/class/lcd/lcd_power (I think that's it (I've switched screens right now)) to turn it off. 2011-01-03 01:58 "0" turns it on... 2011-01-03 01:58 Whee! 2011-01-03 02:00 kewl. now you can use the ben as a flashlight :) 2011-01-03 02:02 Apparently, you can use "fbgrab /sys/class/framebuffer/fb0" (or something like that (I switched screens again!)) to get a screen cap. 2011-01-03 02:03 This sys stuff is very interesting... When I was first using UNIX, we didn't have any of this... 2011-01-03 02:03 There appear to be several fb* tools in /usr/bin... 2011-01-03 02:03 (fb0) isn't there one in /dev, too ? 2011-01-03 02:05 yeah, /sys is somewhat inspired by what sun did on solaris, but with a ton more things added. the new place to dump stuff, after /proc got too messy ;-) 2011-01-03 02:06 Yeah, there's the /dev/fb0, but the sys stuff seems more intended for monitoring and control. 2011-01-03 02:06 I guess like /proc... 2011-01-03 02:09 yes, and /sys also provides the raw data for /dev 2011-01-03 02:11 anyway, the evil day star will be up soon. time for me to crawl to bed ... 2011-01-03 02:12 Quick question before you go... Is there an equivalent of fuser installed on the machine? 2011-01-03 02:12 I thought I could find who has the lock on /dev/fb0 so I could kill it to reset things, but no fuser... 2011-01-03 02:18 Oh, well, I have my own day star to face in about five hours. Probably a good time to call it off... 2011-01-03 03:04 [commit] Wolfgang Spraul: fixed path in Makefile http://qi-hw.com/p/m1/05e9a31 2011-01-03 04:58 wolfspraul: btw, http://qi-hw.com/p/m1/05e9a31 -> unknown host 2011-01-03 04:59 works here 2011-01-03 04:59 hmm, interesting. temporarily. on the 2nd try, it worked 2011-01-03 04:59 unknown host? you mean qi-hw.com doesn't resolve? 2011-01-03 05:00 yeah, didn't resolve. well, false alarm then, sorry. 2011-01-03 05:03 you probably saw that I committed the --plot stuff, and exit code fixes 2011-01-03 05:04 so I think next I will bring some reports/files live on the server, meaning that I automatically generate them upon commits 2011-01-03 05:04 ah, exit code, yes. tested it. works great ! thanks ! 2011-01-03 05:05 haven't played with --plot yet. but if schhist is happy, then i guess it works :) 2011-01-03 05:05 how about the cmdline options now? 2011-01-03 05:05 do you need more? 2011-01-03 05:05 for now, i'm more than satisfied with the ones we have :) 2011-01-03 05:05 ok 2011-01-03 05:06 I need to start communicating with upstream at some point, to make the patch more maintainable. 2011-01-03 05:07 you probably already saw that i automated most of the process for atusb. CAM and toner transfer are done. only the BOM is missing. 2011-01-03 05:07 (upstream) yup :) 2011-01-03 05:07 no I haven't seen it yet 2011-01-03 05:07 too many things 2011-01-03 05:08 but it sounds great! very nice... 2011-01-03 05:09 this should do the trick: cd ben-wpan/atusb/cam2; make 2011-01-03 05:09 then you can "make cng", "make drill", "make mill" 2011-01-03 05:10 well, it won't do much without a mill, but at least the mechanisms are all there 2011-01-03 05:10 and in ben-wpan/atusb itself, "make front" and "make back" print the respective sheets for toner transfer 2011-01-03 05:37 wolfspraul, I got no replies after typing "gtkterm -p /dev/ttyUSB1 -s 115200" 2011-01-03 05:38 adamw_: try this: unplug jtag-serial. run "tail -f /var/log/syslog" on your computer (as root). then connect the jtag-serial again. 2011-01-03 05:39 Jan  3 18:37:54 adam-laptop kernel: [13245.600186] usb 6-1: USB disconnect, address 3 2011-01-03 05:39 Jan  3 18:38:46 adam-laptop kernel: [13296.953092] usb 6-1: new full speed USB device using uhci_hcd and address 4 2011-01-03 05:39 Jan  3 18:38:46 adam-laptop kernel: [13297.095148] usb 6-1: not running at top speed; connect to a high speed hub 2011-01-03 05:39 Jan  3 18:38:46 adam-laptop kernel: [13297.117387] usb 6-1: configuration #1 chosen from 1 choice 2011-01-03 05:41 do you see a new entry in lsusb? 2011-01-03 05:41 btw, in the Windows reflash tool, did you also create a random serial number? 2011-01-03 05:42 ID 20b7:0731 by lsusb 2011-01-03 05:42 in "Hardware Specific, Port A, Hardware", you need to change from RS232 UART to 245 FIFO 2011-01-03 05:42 at least that's what my notes say 2011-01-03 05:42 no , i didn't create a serial number. 2011-01-03 05:42 ok, that shouldn't matter 2011-01-03 05:42 how about the change from RS232 UART to 245 FIFO? 2011-01-03 05:42 wait 2011-01-03 05:43 it seems your Linux machine does not create /dev/ttyUSB devices, don't know why 2011-01-03 05:44 unfortunately I don't have a board here so I cannot try/compare 2011-01-03 05:45 try this: lsusb -v -d 20b7:0731 2011-01-03 05:46 it should list a lot of data, don't paste it here but upload it to pastebin.com 2011-01-03 05:48 it can not be detected in FTDI FT_Prog utility, so i can't see if the change from RS232 UART to 245 FIFO. 2011-01-03 05:49 he. maybe because you switched the vid/pid? 2011-01-03 05:49 yes, i think. 2011-01-03 05:49 go back to Linux and try that lsusb -v -d command 2011-01-03 05:49 upload to pastebin.com? 2011-01-03 05:49 yes 2011-01-03 05:49 my nanonote always disconnects from my machine after 10, 20 seconds after i connect it to my PC. does any of you had such problem and how did you fix it? 2011-01-03 05:50 have you tried that before? it's fun... 2011-01-03 05:50 any suggestion would be greatly appreciated. 2011-01-03 05:50 I remember something on the list about that. 2011-01-03 05:51 wolfspraul, never used pastebin.com   , just try...second 2011-01-03 05:53 wolfspraul, http://pastebin.com/RAuFcdVp 2011-01-03 05:54 great! :-) 2011-01-03 05:54 yeah, it doesn't look configured (flashed) very well 2011-01-03 05:55 bInterfaceClass = Vendor Specific Class 2011-01-03 05:55 adamw_: can you connect your cable to a high speed port? 2011-01-03 05:55 it should work in high speed 2011-01-03 05:57 lekernel, with m1? 2011-01-03 05:57 huh? 2011-01-03 05:57 to a high speed USB port on your computer 2011-01-03 05:57 yes, connected 2011-01-03 05:58 your syslog says otherwise 2011-01-03 05:58 second 2011-01-03 05:59 which parameters will be different? 2011-01-03 05:59 adamw_: it's 0713 (not 0731) 2011-01-03 06:00 Jan  3 18:38:46 adam-laptop kernel: [13296.953092] usb 6-1: new full speed USB device using uhci_hcd and address 4 2011-01-03 06:00 Jan  3 18:38:46 adam-laptop kernel: [13297.095148] usb 6-1: not running at top speed; connect to a high 2011-01-03 06:00 it shouldn't print that 2011-01-03 06:00 but 2011-01-03 06:00 [316014.256182] usb 1-3: new high speed USB device using ehci_hcd and address 3 2011-01-03 06:00 you also flashed the wrong USB ID, which could also explain your other problems 2011-01-03 06:01 oah...man! i changed wrong ID! 2011-01-03 06:02 btw, how can i change my VID in FTDI FT_Prog utility? 2011-01-03 06:02 the same way you change the PID 2011-01-03 06:02 sorry all i did is bother you guys. 2011-01-03 06:02 I'm surprised it's not detected as high speed 2011-01-03 06:02 lsusb output with the cable correctly flashed => http://pastebin.com/AwjFCH5x 2011-01-03 06:03 but i used F5(scan) the FT_Prog didn't see it? 2011-01-03 06:03 well...let me try anther new pod. 2011-01-03 06:03 this problem is explained in the FT_Prog documentation and you should either disable the EEPROM temporarily (so the cable reverts to its default IDs) or modify the driver's INF file to use the new IDs 2011-01-03 06:04 lekernel: hmm, but your device class is also still 'vendor specific' 2011-01-03 06:04 for the serial shouldn't there be some serial device class? 2011-01-03 06:05 adamw_: when you flash again, remember changing "Hardware Specific, Port A, Hardware" from RS232 UART to 245 FIFO 2011-01-03 06:05 the other usb/serial cables I have here also use "vendor specific" class 2011-01-03 06:05 at least that's what I did and it worked well 2011-01-03 06:06 adamw_: on the windows side, you should edit the .inf file to add both 20b7:0713 and the (wrong) 20b7:0731 - then you can easily use FT_Prog when needed 2011-01-03 06:08 the 20b7:0713 in *.inf is correct, just I typed wrong in FT_Prog program. :) 2011-01-03 06:09 yes but now you need to add the wrong one so you can fix that one board 2011-01-03 06:09 that sounds easier than disabling the eeprom 2011-01-03 06:10 connect the board directly to your notebook, not to an external hub 2011-01-03 06:10 I'm still surprised about the high-speed thing, let's see :-) 2011-01-03 06:11 that's the most troubling issue so far 2011-01-03 06:11 but maybe it's only a hub/port/cable problem 2011-01-03 06:24 in windows, it can show "Milkymist USB JTAG 2011-01-03 06:24 " & "Milkymist USB Serial 2011-01-03 06:24 " 2011-01-03 06:25 let's focus on Linux 2011-01-03 06:25 i know why  I got wrong. I just changed the wiki page from "0731" to "0713"...man 2011-01-03 06:25 yeah.. 2011-01-03 06:25 the PID should not matter that much for your testing right now 2011-01-03 06:26 did you connect it directly to your notebook before? or to a hub? 2011-01-03 06:26 direct to notebook. 2011-01-03 06:27 ok where are you now? did you change the PortA/Hardware thing to 245 fifo? 2011-01-03 06:28 yes 2011-01-03 06:28 what does Linux say in /var/log/syslog when you connect the board? 2011-01-03 06:28 tail -f /var/log/syslog 2011-01-03 06:30 new full speed USB device using uhci_hcd and address 10 2011-01-03 06:30 Jan  3 19:29:25 adam-laptop kernel: [16336.119151] usb 5-2: not running at top speed; connect to a high speed hub 2011-01-03 06:30 Jan  3 19:29:25 adam-laptop kernel: [16336.143386] usb 5-2: configuration #1 chosen from 1 choice 2011-01-03 06:35 adamw_: run 'dmesg' and paste the last 20 lines or so in pastebin.com 2011-01-03 06:37 http://pastebin.com/GwJfmEdU 2011-01-03 06:37 lekernel: maybe his ehci/uhci drivers in Linux are messed up? 2011-01-03 06:39 adamw_: try 'lsmod|grep hcd' 2011-01-03 06:39 wpwrak: I suggest using OVP components built to purpose. USB2.0 parasitary capacitance is rather insanely low 2011-01-03 06:40 wolfspraul, no reply after 'lsmod|grep hcd' 2011-01-03 06:40 lekernel: on the other hand, why would the low-speed/high-speed problem prevent ttyUSB from showing up? 2011-01-03 06:41 adamw_: try the gtkterm thing again, on /dev/ttyUSB0 and /dev/ttyUSB1 2011-01-03 06:41 I don't think they have been created though... 2011-01-03 06:41 ok..second 2011-01-03 06:42 what kernel do you have? (run 'uname -a') 2011-01-03 06:43 no work, i remember gtkterm can let me scroll to select /dev/ttyUSB0 or ttyUSB1 2011-01-03 06:46 run lsusb -v -d 20b7:0713 again (pastebin), I'm wondering whether the interface class is now different... 2011-01-03 06:46 I mean I don't know why your Linux should know there is a serial port there 2011-01-03 06:47 wpwrak: sparkgaps are nice... for circuits with electron tubes 2011-01-03 06:49 and happy new year @ everybody 2011-01-03 06:50 wolfspraul, http://pastebin.com/m4hK8me5 2011-01-03 06:52 happy new year to you too! 2011-01-03 06:53 lekernel, do i need to do http://www.milkymist.org/wiki/index.php?title=Working_ftdi_eeprom 2011-01-03 06:53 ok. manufacturer, product and serial strings are still not set, but that shouldn't matter. 2011-01-03 06:54 no you don't need ftdi_eeprom 2011-01-03 06:54 can you run 'uname -a'? 2011-01-03 06:54 unfortunately I don't have a board, and I'm not clear what makes Linux detect the ttyUSB. only lekernel can help :-) 2011-01-03 06:55 Linux adam-laptop 2.6.32-27-generic #49-Ubuntu SMP Wed Dec 1 23:52:12 UTC 2010 i686 GNU/Linux 2011-01-03 06:57 it seems Windows can detect the serial port? 2011-01-03 06:57 yes 2011-01-03 06:57 it shows 2011-01-03 06:58 do you have a serial terminal software in Windows? 2011-01-03 06:58 hmm...let me try to use it in windows 2011-01-03 07:03 which Windows version do you have? if it's old, there may be a software called 'HyperTerminal' 2011-01-03 07:03 I think they removed it in Vista though 2011-01-03 07:06 you are right 2011-01-03 07:06 i am installing Teraterm Pro 2011-01-03 07:11 does anybody know how to check for low-speed/high-speed usb device setup in Windows? 2011-01-03 07:12 adamw_: your Windows machine and your Linux machine are two different notebooks, right? 2011-01-03 07:12 right 2011-01-03 07:15 wolfspraul, hey now i used Tera term Pro in windows with feedback (RX/TX) worked well. 2011-01-03 07:22 well at least that :-) 2011-01-03 07:22 do you have a usb memory stick? 2011-01-03 07:23 I am wondering whether your Linux notebook supports USB high speed at all... 2011-01-03 07:23 wolfspraul: I do not know what low-speed and high-speed means yet :) is that usb 1.0 and 2.0 ? 2011-01-03 07:23 how old is the Linux notebook? 2011-01-03 07:23 zrafa: yes 2011-01-03 07:23 if you have a usb memory stick, try connecting it and let me know what /var/log/syslog says 2011-01-03 07:23 kristianpaul: great, at least I guessed well ;) 2011-01-03 07:23 try different usb ports is good idea, some laptops dont have all of then in 2.0 mode 2011-01-03 07:24 true, good idea 2011-01-03 07:24 adamw_: pastebin the output for lsusb with NO usb device connected 2011-01-03 07:25 that usually tells:  Linux Foundation X.X  root hub 2011-01-03 07:25 kristianpaul, with lsusb -??? 2011-01-03 07:25 so X.X may be 1.1 or 2.0 i hope :-) 2011-01-03 07:25 adamw_:  no - 2011-01-03 07:25 jsut lsusb 2011-01-03 07:26 just* 2011-01-03 07:26 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 2011-01-03 07:26 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 2011-01-03 07:27 good you seems to have 2.0 USB ports :-) 2011-01-03 07:27 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub 2011-01-03 07:27 arg 2011-01-03 07:27 which one was the jtag-serial board connected to earlier? 2011-01-03 07:27 i have three usb ports and all i tested 2011-01-03 07:28 no show ttyUSB1 or USB0 2011-01-03 07:28 :/ 2011-01-03 07:28 well, I am not sure those 2 things are connected 2011-01-03 07:28 why would ttyUSB not work if in low speed? 2011-01-03 07:29 adamw_: what is your current linux based distro? 2011-01-03 07:29 uname -r 2011-01-03 07:29 [19906.712572] usb 5-2: FTDI USB Serial Device converter now attached to ttyUSB0 2011-01-03 07:29 [19906.712628] usbcore: registered new interface driver ftdi_sio 2011-01-03 07:29 [19906.712633] ftdi_sio: v1.5.0:USB FTDI Serial Converters Driver 2011-01-03 07:29 aha 2011-01-03 07:29 what's that? 2011-01-03 07:29 :D 2011-01-03 07:30 i can easily do a FDTI USB>TTL cable 2011-01-03 07:30 oh :-) 2011-01-03 07:30 not the problem cable 2232H 2011-01-03 07:31 first you should try to get the serial port to work 2011-01-03 07:31 linux needs to create ttyUSB devices 2011-01-03 07:31 so i just don't know why my linux laptop can not detect /show ttyUSB1 2011-01-03 07:32 but it can work in windows as well while running Tera Term 2011-01-03 07:32 can you connect the jtag-serial, then pastebin lsusb -v 2011-01-03 07:32 (just -v, for all devices) 2011-01-03 07:32 second 2011-01-03 07:34 if the Linux kernel doesn't know the vid/pid, and it also has no recognizable interface class, how can it create a serial device? 2011-01-03 07:34 I don't get it. There must be more. 2011-01-03 07:35 http://pastebin.com/PXjnSjxV 2011-01-03 07:38 how many external USB connectors does your notebook have? 2011-01-03 07:38 right now the jtag-serial board seems to be connected to a 1.1 hub 2011-01-03 07:39 so is a Logitech mouse 2011-01-03 07:40 three ports 2011-01-03 07:40 i typed 'ls /dev/ttyUSB1' to each port after I plugged 2011-01-03 07:41 adamw_: did you tried type also dmesg after you pluged (to get a better debug) ? 2011-01-03 07:42 all not detected jtag-serial 2011-01-03 07:42 one by one 2011-01-03 07:42 maybe the board just works fine 2011-01-03 07:42 kristianpaul, YES 2011-01-03 07:43 I keep saying that I don't know why Linux would detect the ttyUSB device. earlier lekernel seemed to say that if it's not detected as high-speed, then it won't setup the ttyUSB? 2011-01-03 07:43 but I wouldn't know why 2011-01-03 07:43 i didn't see any like 'attached to /dev/ttyUSB0 or /dev/ttyUSB1' 2011-01-03 07:43 so maybe we have 2 problems right now: 2011-01-03 07:43 1) your notebook does not have external usb 2.0 (high-speed) ports 2011-01-03 07:43 maybe all 3 external ports are 1.1 2011-01-03 07:44 2) it is not clear (to me) how Linux detects the ttyUSB devices, whether that can only work in high-speed 2011-01-03 07:44 worst case we run the whole test in Windows 2011-01-03 07:44 so for 1) how can we easily make sure my linux laptop built with 2.0 (high-speed)? 2011-01-03 07:45 it is 'built', but not sure about the external connectors 2011-01-03 07:45 you have 3, right? 2011-01-03 07:45 yes, 3 ports 2011-01-03 07:45 1 has the jtag-serial now, another one has the logitech mouse, right? 2011-01-03 07:45 how about the 3rd one. move the jtag-serial from where it is now to the 3rd one. 2011-01-03 07:45 (the empty one) 2011-01-03 07:45 then pastepin lsusb -v again 2011-01-03 07:45 the others two I unplugged 2011-01-03 07:46 before when you ran lsusb, you had jtag-serial and logitech connected 2011-01-03 07:46 ok....let me do three times again with only jtag-serial 2011-01-03 07:46 move jtag-serial to the one that was _not_ used by jtag-serial or logitech before 2011-01-03 07:46 we already know that the port you had jtag-serial before, and logitech before, are both 1.1 2011-01-03 07:46 so you only need to try the 3rd one 2011-01-03 07:48 now..i was confused...so let me do each usb port and pastebin.com 2011-01-03 07:53 usb port1 : http://pastebin.com/qiYtpPaW 2011-01-03 07:56 usb port2 : http://pastebin.com/1iEP44FF 2011-01-03 07:57 on Windows, you can try something like this http://www.nirsoft.net/utils/usb_devices_view.html 2011-01-03 07:58 usb port3 : http://pastebin.com/LFXqw1EF 2011-01-03 08:01 hmm seems to me that 2.0 port is not externally wired 2011-01-03 08:02 kristianpaul, what did you mean? 2011-01-03 08:03 adamw_: 1) your notebook does not have external usb 2.0 (high-speed) ports 2011-01-03 08:03 Are you meaning that there's no 2.0 port in my all 3 ports ? 2011-01-03 08:03 yes 2011-01-03 08:03 s/wired/wiking 2011-01-03 08:03 wiring* 2011-01-03 08:03 ok but that's a side issue 2011-01-03 08:04 we are trying to test the jtag-serial boards 2011-01-03 08:04 adamw_: on your Linux notebook, we cannot test high-speed right now. 2011-01-03 08:04 but back to the jtag-serial board - it only works in high-speed mode? 2011-01-03 08:09 ft2232h datasheet says high-speed and full-speed compatible 2011-01-03 08:10 so why are the ttyUSB not being created? 2011-01-03 08:11 or the other way round - how can Linux know there is a serial device there? 2011-01-03 08:14 adamw_: random attempt :-) try 'modprobe usbserial' 2011-01-03 08:15 what's it? 2011-01-03 08:16 no reply 2011-01-03 08:16 after typing 2011-01-03 08:16 dmesg 2011-01-03 08:17 type 'modprobe usbserial' after dmesg? 2011-01-03 08:18 I'm reading about a kernel bug... http://ubuntuforums.org/showthread.php?t=1592318 2011-01-03 08:19 which appeared in 2.6.32-25 (and you are on -27, very close) 2011-01-03 08:19 hmm..ok 2011-01-03 08:20 maybe scrap Linux and just test on Windows 2011-01-03 08:20 I have no board here, I cannot effectively help you debug it. 2011-01-03 08:20 you have no known-good board either, and were not able to prepare for the testing in advance. 2011-01-03 08:21 you already can verify the serial port in Windows, the only thing that remains is a quick jtag test 2011-01-03 08:21 yeah.. 2011-01-03 08:21 not sure you have full-speed or high-speed in Windows 2011-01-03 08:21 but all linux commands depends on device name, isn't it? 2011-01-03 08:22 I don't have complete overview. 2011-01-03 08:22 the vid/pid is quite important 2011-01-03 08:22 and I think the 'interface class' too, but that may be wrong already 2011-01-03 08:22 the strings should not be important, but who knows, someone may also look at those 2011-01-03 08:23 when you reflash, remember to set the iManufacturer, iProduct and iSerial strings 2011-01-03 08:23 for the iSerial, just let FT_Proc create a unique/random number 2011-01-03 08:23 iManufacturer = Qi Hardware 2011-01-03 08:23 iProduct = Milkymist One JTAG/serial 2011-01-03 08:24 you can check with lsusb -v -p 20b7:0713, the boards you are making should look like http://pastebin.com/AwjFCH5x 2011-01-03 08:24 except that the iSerial should be unique on each board 2011-01-03 08:25 also back when I flashed them, in FT_Prog I set this "Hardware Specific, Port A, Hardware" from RS232 UART to 245 FIFO 2011-01-03 08:26 I suggest you only flash and test 20 now. 2011-01-03 08:26 that's enough 2011-01-03 08:27 no need to waste time with the other 80, since we will most likely fine-tune this setup, looking at the confusion we are facing right now :-) 2011-01-03 08:27 yeah..i can sure I did a unique/random number in FT_Proc 2011-01-03 08:27 just play around a little 2011-01-03 08:27 we don't know much, and have few boards to compare with/debug 2011-01-03 08:27 maybe when lekernel is back he can correct some of our assumptions... 2011-01-03 08:28 from what you see in Windows, it seems that flashing works, and serial works too 2011-01-03 08:28 that's a good sign 2011-01-03 08:28 just need to find a way to check jtag from Windows 2011-01-03 08:28 yeah...I'll try to reflash Manufacturer name 2011-01-03 08:28 and maybe see whether the board is recognized and operating in high-speed mode 2011-01-03 08:28 I pasted a link to some free software above, maybe that helps. 2011-01-03 08:28 yeah...I'll try it 2011-01-03 08:29 http://www.nirsoft.net/utils/usb_devices_view.html 2011-01-03 08:29 this one 2011-01-03 08:29 looks similar to lsusb 2011-01-03 08:29 I haven't tried, I have no Windows. 2011-01-03 08:29 also maybe I directly use xilinx tool to test if jtag function is ok 2011-01-03 08:29 on Linux? 2011-01-03 08:29 on windows 2011-01-03 08:29 hmm 2011-01-03 08:29 but I didn't try...before 2011-01-03 08:30 not sure it works, there may also be problems in recognizing the board 2011-01-03 08:30 maybe if you flash the vid/pid to be the same as in the xilinx cable it can work? 2011-01-03 08:30 so need to check somewhere document is 2011-01-03 08:30 there are quite a few switches and settings, and ftdi variants... 2011-01-03 08:30 I think it's messy anyway, we are not well prepared. So just find whatever way you think the boards are working. serial and jtag. 2011-01-03 08:30 only test 20. 2011-01-03 08:31 then we need to improve this whole process in Linux 2011-01-03 08:31 (later) 2011-01-03 08:32 ok... 2011-01-03 08:33 you tested serial already, just need to find a way to test jtag :-) 2011-01-03 08:33 with serial working, I'd say things look good 2011-01-03 08:33 I'm an optimist... 2011-01-03 08:33 yeah...via Tera Term Pro, it works well 2011-01-03 08:34 well...i try my self to find if using xilinx tool in windows to test jtag. 2011-01-03 08:35 I can imagine that the xilinx tool will look for specific pid/vid numbers. 2011-01-03 08:35 once I success in window and read Spartan 6 id back then the jtag/serial run should be all fine 2011-01-03 08:35 so unless you reflash the jtag-serial boards with the vid/pid usb ids that the xilinx software expects, it may not work with the jtag-serial board 2011-01-03 08:35 of course I'm guessing 2011-01-03 08:36 or maybe you can tell the xilinx software somehow to accept 20b7:0713 2011-01-03 08:36 and to understand that it is a ftdi 2232 with jtag on port a 2011-01-03 08:36 but I still feel strange why my linux laptop is 1.1 not 2.0 2011-01-03 08:36 the 2.0 is internal 2011-01-03 08:36 the external connectors (seem) all to be 1.1 2011-01-03 08:36 the notebook is 4 years old, right? 2011-01-03 08:36 hmm....i checked official web...it said 2011-01-03 08:37 what notebook model is it? 2011-01-03 08:37 ha...bad...it's really 2.0 internal only 2011-01-03 08:37 btw - I really think the low-speed high-speed discussion is besides the point. 2011-01-03 08:37 http://www.fujitsu.com/cn/services/hardware/pc/lifebook/v/v1020-4.html 2011-01-03 08:37 according to the 2232 datasheet the chip should support both 2011-01-03 08:38 so there are more configuration issues on the Linux side, not just low-speed 2011-01-03 08:38 V1020 model , Fujitsu 2011-01-03 08:38 both serial & jtag _should_ work with low-speed as well, I think 2011-01-03 08:39 hmm...I'll check 2232 jtag/serial circuit again tonight 2011-01-03 08:39 it works in Windows 2011-01-03 08:39 I'd focus on that 2011-01-03 08:40 well...i need to have dinner now, 2011-01-03 08:40 see you later 2011-01-03 08:40 enjoy 2011-01-03 08:40 thanks a lot! 2011-01-03 09:03 arggg openmoko support for wikireader sucks :( 2011-01-03 09:04 why? 2011-01-03 09:06 The wikireader i have to my mother for chrismas jsut got bricked 2011-01-03 09:06 I debug my self the SD card and seems dead, no fdisk, no dmesg recognize it 2011-01-03 09:06 I write that to OM support 2011-01-03 09:07 They first askme to do silly procedure of taking SD & Batterues back and put it again 2011-01-03 09:07 Now i reply with a: i dint work 2011-01-03 09:08 please tell how to debug SD, i *bought* a bran new SD from kingstone 2011-01-03 09:08 They reply: ok, send us the device back to Sandiego, CA, we can see what was wrong with it.. 2011-01-03 09:08 bah 2011-01-03 09:09 Thats 50usd i'm not going to pay more for it, i already pay around 160USD just to have in holliday 2011-01-03 09:35 kristianpaul: better would say to buy two nns and work on better wikireader for it :) 2011-01-03 09:35 would say= would be 2011-01-03 09:36 zrafa: my mother is not good with keyboards.. 2011-01-03 09:36 no good at all and no hope it will change 2011-01-03 09:37 I like the wikiriader i have from you btw :-) 2011-01-03 09:37 kristianpaul: you could disable several keys on nns, so it looks like OM wikireader :) 2011-01-03 09:37 lol 2011-01-03 09:37 any way i formally close this off-topic chat, sorr for the noise i was a bit biased and angry 2011-01-03 09:56 DocScrutinizer: (OVP and USB 2.0) high-speed is a pain, yes. but full-speed is a lot more relaxed. and the components are cheaper, too. TVS are quite pricey for what they are. 2011-01-03 09:57 yep 2011-01-03 09:57 we have sorted out the jtag-serial stuff in the #milkymist channel 2011-01-03 09:58 "modprobe ftdi_sio vendor=0x20b7 product=0x0713" did the trick 2011-01-03 09:58 all moving now :-) 2011-01-03 09:58 DocScrutinizer: (happy new year) you too ! :) 2011-01-03 09:58 :-D 2011-01-03 09:58 DocScrutinizer: Dieter didn't make it to 27c3 either in the end, he got snowed in. 2011-01-03 09:58 ooh 2011-01-03 09:59 zrafa: (usb 2.0) its a bit more complex. usb 1.0, usb 2.0, etc. are the versions of the standard. then you have low-speed, full-speed, high-speed, and soon yet another thing (don't know what they called it - "insane speed" perhaps ? :) 2011-01-03 09:59 super speed? 2011-01-03 09:59 :-) 2011-01-03 09:59 zrafa: now usb 1 only defined low and full speed. usb 2 defines everything in usb 1 plus high-speed 2011-01-03 10:00 zrafa: so if a product says "usb 2.0", it can still be only high- oder even low-speed. needless to say, this is rather confusing. 2011-01-03 10:02 hmm confusing indeed 2011-01-03 10:10 wolfspraul: (usb 1.1 vs. usb 2.0 hub) do you know that, if you have a EHCI (the high-speed controller), that you also have an OHCI/UHCI (low/full-speed) in parallel ? 2011-01-03 10:11 wolfspraul: (usb) the EHCI only does high-speed. if your device is something else, it gets rerouted to the UHCI/OHCI 2011-01-03 10:14 wolfspraul: so it seems unlikely to me that thus 4 yo laptop would only have 1.1 ports on the outside. possible explanations for not detecting a high-speed device as high-speed would include: 1) kernel somehow not configured to support it (not terribly likely with ubuntu, but you never know), 2) some odd bios setting that disables the EHCI, 3) some mystery bit in the FTDI that makes it not ask for high-speed, or 4) some hardware flaw t 2011-01-03 10:14 hat makes high-speed negotiation fail. 2011-01-03 10:15 wolfspraul: did adam try to insert a usb flash stick ? 2011-01-03 10:15 I don't think so. 2011-01-03 10:15 we have put this high-speed thing aside for now. 2011-01-03 10:16 I thought he googled that his notebook indeed only has usb 1.1 on the outside? 2011-01-03 10:16 don't worry about it. maybe he needs to buy a new notebook anyway, and then switch to fedora right away... 2011-01-03 10:16 that thing he has right now is old 2011-01-03 10:17 the link he posted seems to say only usb 2.0: http://www.fujitsu.com/cn/services/hardware/pc/lifebook/v/v1020-4.html 2011-01-03 10:19 the tricky bit with using different machines is that sometimes your problems come from the capacitative load. e.g., the first atusb boards had TVSs of 330 pF on the USB lines. they worked flawlessly with my PC and my fujitsu laptop. then i connected them to the OQO a few days ago. lo and behold, they didn't even enumerate. 2011-01-03 10:20 of course, 330 pF is way too high. (what's allowed are 50 pF) after removing those little monsters, the boards worked fine. 2011-01-03 10:23 (i used those 330 pF critters, because a) i hadn;t foung the limit back then (it's a bit hidden in the standard. they write a lot about low-speed and then even more about high-speed, but the full-speed load limit is conveniently placed only in the caption of a figure), and b) becasuse i had hoped to make the board easily diy-makeable :) 2011-01-03 10:35 wolfspraul: another issue with the ftdi chips: their horrible lack of documentation makes linux support unreliable, particularly when it comes to the eeprom utility (ftdi_eeprom). it's not so bad for the really old chips, but more recent ones can have issues. e.g., with the FT232RL, the default use set an endpoint size to zero, so the chip would enumerate, but any attempt to send bulk data with libusb would fail, with the kernel compla 2011-01-03 10:35 ining that the message was too large. 2011-01-03 10:35 I know. We are working on making all of this work flawlessly out of the box, but it will take some time. 2011-01-03 10:36 wolfspraul: so your approach of trying with the official windows tools first has some merits (i guess you didn't expect me to say that :) 2011-01-03 10:37 well, or at least s/windows/proprietary/ 2011-01-03 10:37 yeah well. this jtag-serial run is a little less organized than normally anyway. 2011-01-03 10:37 I am gambling that the board is so simple that not much can go wrong :-) 2011-01-03 10:38 so I sent all 3 working boards to Sebastien, leaving 0 for Adam. That would be a total no-no for any normal product. 2011-01-03 10:38 (not much can go wrong) about one month if fighting the ft232rl taught me otherwise ;-) 2011-01-03 10:38 essentially Adam has to make 100 of a totally unknown board (for him), right away. No testing preparations, just make them then find out whether they work :-) 2011-01-03 10:38 yes I know, it's risky. I am crossing my fingers. 2011-01-03 10:39 Sebastien needed his 3. If Adam would have had one the last month or so things would be much more controlled. 2011-01-03 10:39 but this way, they are more fun :-) 2011-01-03 10:39 do sebastien's work ? 2011-01-03 10:40 yes 2011-01-03 10:40 it'll be fine. 2011-01-03 10:40 yeah the boards aren't too expensive, so it's not too big a gamble, i guess 2011-01-03 10:40 next time we raise the standards a little. 2011-01-03 10:40 in a way, at least the lowering of standards was on purpose / controlled. controlled chaos... 2011-01-03 10:40 if sebastien got his three to work, then the chances of adam eventually succeeding should be rather good :) 2011-01-03 10:40 oh of course 2011-01-03 10:41 those boards worked even before I sent them to sebastien 2011-01-03 10:41 "controlled flight into terrain" (-:C 2011-01-03 10:41 the board was designed by Yanjun Luo 2011-01-03 10:41 and he soldered (by hand!) 4 of them 2011-01-03 10:41 they all worked 2011-01-03 10:41 he kept 1, gave me 3 2011-01-03 10:41 aah, so the 3 are not from the same batch as adam's. i see. 2011-01-03 10:41 after consideration, I decided to give all 3 to Sebastien, even though it was risky on Adam's side 2011-01-03 10:41 that's why Adam is scramling (a little) right now 2011-01-03 10:42 no not at all. the pcb was made elsewhere, the sourcing was elsewhere. 2011-01-03 10:42 you should have bribed yanjun to make one more :) 2011-01-03 10:42 crystal was changed, headers were changed, one usb bug (high-speed related :-)) was fixed 2011-01-03 10:42 and then 100 right away, and first time for adam to ever have a working one in his hands 2011-01-03 10:43 this is not the right way to do things, I know. but whatever. some tough decisions here... 2011-01-03 10:43 at least it's a global collaborative project 2011-01-03 10:43 yeah. i known to be good unit would have helped adam at least with the host software side 2011-01-03 10:43 sure 2011-01-03 10:43 but well, no risk, no fun :) 2011-01-03 10:43 we decided against it ;-) (sorry Adam...:-)) 2011-01-03 10:44 and adam's learning experience will be more profound ;-) 2011-01-03 10:49 wpwrak: I see adam slowly developing hardcore foss survival techniques, like 'when in doubt what to do in a directory, just run make and see what happens' 2011-01-03 10:49 if he continues down that road, he will be really good in a while :-) 2011-01-03 10:50 hehe :) 2011-01-03 10:53 have you guys seen the clock oofoe made? 2011-01-03 10:54 (I believe he called himself oofoe1 here) 2011-01-03 10:54 no - clock? 2011-01-03 10:55 http://love2d.org/forums/viewtopic.php?f=5&t=2306 2011-01-03 10:57 oh yeah 2011-01-03 10:57 bartbes: nice! 2011-01-03 10:57 and that picture is really bad 2011-01-03 10:57 :P 2011-01-03 10:57 let's get this included in the images 2011-01-03 10:58 heh 2011-01-03 10:58 I was waiting for him to show 2011-01-03 10:58 *+up 2011-01-03 10:58 nlove could become really great on the NanoNote, of course I know many details are still missing, but I'm hopeful... 2011-01-03 10:58 so we could talk about adding the battery indicator 2011-01-03 10:58 alright, I got a better picture 2011-01-03 10:59 not quite focused, but at least you can see what's going on 2011-01-03 11:01 http://bartbes.ath.cx/clock_on_nlove.jpg 2011-01-03 11:01 incidentally the nn's clock is off 2011-01-03 11:01 but meh, who cares 2011-01-03 11:02 we need some good nlove screenshots 2011-01-03 11:02 taken on the device, clean 320x240 png 2011-01-03 11:02 oh.. 2011-01-03 11:02 I totally forgot about fbgrab 2011-01-03 11:02 heh, well, I guess you would see no diff if I were to run the clock on my comp 2011-01-03 11:02 (yay, cross-platform!) 2011-01-03 11:02 he 2011-01-03 11:03 that's not nice :-) 2011-01-03 11:03 anyway, I guess I need to put some more work into the graphics 2011-01-03 11:03 and get some games out 2011-01-03 11:04 in fact, I recently heard nlove might be popular in the caanoo scene 2011-01-03 11:04 I shall investigate 2011-01-03 11:04 that'd be awesome 2011-01-03 11:05 madness, looking for uses of your own program 2011-01-03 11:05 :P 2011-01-03 11:07 124 downloads on openhandhelds.org 2011-01-03 11:07 I didn't even know they mirrored :O 2011-01-03 11:46 wpwrak: thanks for the clarification! ;) 2011-01-03 12:09 zrafa: ah, and wolfgang was right. the new speed with usb 3.0 is called "SuperSpeed" (3.2-5 Gbps, depending on how you interpret it) 2011-01-03 12:38 http://alxa.ru/file/wallpaper/usb_horror.gif 2011-01-03 12:39 *grin* 2011-01-03 12:53 :S 2011-01-03 13:52 wow, boom picked up a TVS for a LED. now, how did i get it to do that ? ;-) 2011-01-03 13:54 hey guys, i thought maybe one of you have a better knowledge about the current state of the nanonote and could reply to this nice fella: http://boards.dingoonity.org/ben-nanonote/does-it-worth-buying-ben-nanonote-for-retro-hacking/ 2011-01-03 13:58 well you covered it nicely 2011-01-03 13:58 I think 'n'love = nanonote love 2011-01-03 13:58 wolfspraul, my knowledge is quite outdated 2011-01-03 13:58 your post does sound a bit depressing though :-) 2011-01-03 13:58 wolfspraul, yeah, it is sort of true though 2011-01-03 13:59 if nanonote had an easier in use toolchain, i'd port a lot more stuff to it 2011-01-03 13:59 wolfspraul: funny - after an eeschema --bom, eeschema comes up with a black background 2011-01-03 13:59 hmm 2011-01-03 13:59 I've seen that too 2011-01-03 13:59 maybe some settings get saved 2011-01-03 13:59 zear: jlime has a very nice toolchain 2011-01-03 13:59 wolfspraul: nlove == nanonote love sounds like a nice name for a nanonote distribution :) 2011-01-03 13:59 wpwrak, which doesn't work for me 2011-01-03 13:59 zear: how come / 2011-01-03 13:59 zear: nah 2011-01-03 13:59 wpwrak, first, rafa left a lot of default settings in the config files 2011-01-03 14:00 like sdl-config 2011-01-03 14:00 zear: there is a proper toolchain on qi servers 2011-01-03 14:00 zear: jlime toolchain I mean 2011-01-03 14:00 and the second is, for some reason i can't get a simple helloworld to compile 2011-01-03 14:00 zear: the old at jlime.com is bad built 2011-01-03 14:00 while rafa, on the exact same toolchain, can compile everything 2011-01-03 14:00 zrafa, why didn't you tell me? :D 2011-01-03 14:00 zear: you should use that one if you want to work a bit again ;) 2011-01-03 14:00 zrafa, that should be sweet 2011-01-03 14:01 zear: xiangfu wrote up this... http://lists.en.qi-hardware.com/pipermail/discussion/2010-December/006622.html 2011-01-03 14:01 also, nice to see you online again :) 2011-01-03 14:01 zear: because you was a bit tired and frustrated with your nn and broken screen 2011-01-03 14:01 zrafa, my screen is fine if i don't wiggle with it 2011-01-03 14:01 zear: if your host is 64 bit, then you may need some small tweaks to make it work. but once it works, it's very comfty 2011-01-03 14:01 wpwrak, nah, it's x86 2011-01-03 14:02 oh good point. that sdk I pointed to is 64-bit. 2011-01-03 14:02 wpwrak, i don't remember the exact error i was getting, but the same error with dingux toolchain meant the toolchain was placed in the wrong path 2011-01-03 14:02 but we've double checked with rafa and everything seemed to be correctly installed 2011-01-03 14:02 so you have a 32-bit system? 2011-01-03 14:02 wolfspraul, yes, a 32 bit gentoo 2011-01-03 14:02 zear: maybe just try rafa's latest and see if it works now ? 2011-01-03 14:02 zear: the link to the jlime toolchain and instructions are here : http://en.qi-hardware.com/wiki/Jlime 2011-01-03 14:02 wpwrak, yeah, i'll have to try this 2011-01-03 14:03 zear: one of the nice features is that you can install .ipkg packages into your build environment. so if you need some exotic library, you just install the -dev package and you're good. 2011-01-03 14:03 zear: again.. the old one worked for me because my local settins. But the toolchain was not properly built. SO forget that. We tried to fix that one because we did not have the proper one (which we have now) 2011-01-03 14:04 zrafa, sounds great now 2011-01-03 14:04 i'll check it out sooner or later 2011-01-03 14:04 wolfspraul: the xiangfu link you put here looks like xiangfu did the same mistake like me to prepare a sdk or toolchain 2011-01-03 14:05 wpwrak, i prefer a "non-interactive" kernel where i don't need to use any package managers to install extra apps 2011-01-03 14:05 wolfspraul: I will try to talk him about.. it should not have a hardcoded DIR or local settings from his environment 2011-01-03 14:06 and where i can do just export PATH="${PATH}:/path/to/my/toolchain" and not play with any weird commands like with the openmoko toolchain ;) 2011-01-03 14:06 wolfspraul: I did the same, and now check how tired is zear after to try with me to use a bad toolchain 2011-01-03 14:06 :) 2011-01-03 14:06 zrafa, i basically have some other stuff to do for today ;) 2011-01-03 14:06 i'll try it out in the near future though 2011-01-03 14:06 zear: huh ? are you seriously claiming packages are a bad thing ? 2011-01-03 14:06 zear: no problem, I have not with a lot of time either 2011-01-03 14:06 zear: so just try whenever you want 2011-01-03 14:07 wpwrak, no, but i like when you have everything in your toolchain already and you don't need to worry about installing extra packages 2011-01-03 14:07 zear: doesn't have much to do with the kernel, by the way 2011-01-03 14:07 because sooner or later you'll break your toolchain with some dependencies you downloaded from the repo :D 2011-01-03 14:07 zear: well, but we can not put all the 15.000 packages on toolchain 2011-01-03 14:07 wpwrak: does the background change after --bom bother you a lot? 2011-01-03 14:07 wpwrak, i meant non-interactive toolchain, sorry ;D 2011-01-03 14:07 better if we install them when we need 2011-01-03 14:08 if not I will just wait a little and see what accumulates. I have seen this one but wasn't alert enough to investigate on the spot. 2011-01-03 14:08 zear: well, the toolchain has the basics. but there's just too much stuff around for an installation of everything to make much sense. besides, some things probably conflict with each other in some ways. 2011-01-03 14:08 zrafa, i know, i guess i'm just used to gaming devices' toolchains, where all you need can be fit in a ~50M toolchain file 2011-01-03 14:08 zear: and we can add stuff with just a command (with opkg-target). It is really easy. 2011-01-03 14:08 wolfspraul: only until i find out how you managed to make this happen ;-) (it's easy to revert - change the preferences. even if you don't save them, they "stick". more magic.) 2011-01-03 14:09 wolfspraul: (saw it) good. so it's not just some local quirk :) 2011-01-03 14:09 btw zrafa, what was miriam's eeepc's model? 2011-01-03 14:09 it's probably saved automatically 2011-01-03 14:09 I am not surprised 2011-01-03 14:09 there are so many load and save config calls all over the sources, unbelievable 2011-01-03 14:10 sigh. it's just a little odd that it also auto-saves if you have a "save" button right there 2011-01-03 14:10 I am setting the background to black. I probably need to be more diligent, find out where it's saved, and then revert to the original value at the right time. 2011-01-03 14:11 not surprised. from looking at the sources the config stuff is really messy. 2011-01-03 14:11 lots of defaults, overrides, read, write, etc. 2011-01-03 14:11 zrafa: how big is your package repository ? ;-) 2011-01-03 14:11 in some places they even reload because they don't trust what's in memory... 2011-01-03 14:11 ;-))) 2011-01-03 14:12 let's just accumulate a few more bugs then I'll fix them in one go 2011-01-03 14:12 if you want it fixed, let me know 2011-01-03 14:12 btw, why do you set the background to black when generating a BOM ? 2011-01-03 14:12 (fixed) yeah, no hurry 2011-01-03 14:12 good point, just a bad flow 2011-01-03 14:13 I just need to look into it, no problem other than time. 2011-01-03 14:14 I'm most concerned about maintenance overhead when upticking KiCad, that will be interesting. 2011-01-03 14:14 zear: eeepc 900 2011-01-03 14:14 zear: I guess that asus does not make it anymore 2011-01-03 14:15 zrafa, i bought exactly the same model then :D 2011-01-03 14:15 zear: haha.. :D 2011-01-03 14:15 and if it wansn't for the meeting, i probably wouldn't decide to purchase one 2011-01-03 14:15 anyone tried to use fbreader? 2011-01-03 14:15 zear: we are using linux mint there.. really nice and fast 2011-01-03 14:15 i really liked the size factor and how it presents in general 2011-01-03 14:16 zrafa, i'll remember to bug you a bit about it once i get it in mail 2011-01-03 14:16 the one i bought (secondhand) comes with xandros preinstalled 2011-01-03 14:16 zear: that sucks (xandros) 2011-01-03 14:17 but the seller was so nice to call me and apologise for the preinstalled linux, assuring me i can reflash to xp in no time ;D 2011-01-03 14:17 zear: warning: I think that there is a tiny really tiny fat partition (maybe 5mb). dont delete that one 2011-01-03 14:17 zrafa, what would happen if i did so? 2011-01-03 14:17 is xandros upstream still around ? i think the eebox or whatever it is called i got for my tv also had xandros. couldn't even update the distro :) 2011-01-03 14:17 zear: it is really OT, we can continue at jlime or private :) 2011-01-03 14:18 sure ;) 2011-01-03 14:18 zrafa: now that we all are curious about what happens ;-) 2011-01-03 14:18 wpwrak: haha :D 2011-01-03 14:18 wpwrak: repositoy: I guess that around 15000 packages :) 2011-01-03 14:19 zrafa: any idea how many MB ? ob kinda curious how it relates to zear's 50 MB 2011-01-03 14:19 wpwrak: xandros: the eeepc just let you install pacakges from some asus repo IIRC, few packages and xandros really sucks for me 2011-01-03 14:19 s/ob/i'm/ 2011-01-03 14:19 wpwrak: zear's 50 MB is a toolchain for linux game consoles.. which brings with SDL, allegro, etc.. libraries used by games 2011-01-03 14:20 zrafa, not allegro, i failed to properly port it 2011-01-03 14:20 but sdl, vorbis and stuff like that 2011-01-03 14:25 for curious: http://code.google.com/p/dingoo-linux/downloads/detail?name=dingux_toolchain_20091022.tar.bz2&can=2&q= 2011-01-03 14:25 hmm, there's a bug in boom's price selector. if picking a part X that also satisfies the requirements for part Y, then it'll use X for both, even if there was a cheaper choice for Y. something to fix in the rewrite ... 2011-01-03 14:28 yay seems i finally i'm not getting repeated data in a common pattern 2011-01-03 14:30 with the ring buffer ? 2011-01-03 14:31 well i dint changed that part of the code 2011-01-03 14:31 Actually i just modified the C code was polling data 2011-01-03 14:31 It was pointing a fixed address now i points the whole 1024 registers in secuence 2011-01-03 14:34 ah. so what did you change then to make it work ? 2011-01-03 14:34 That make me thing if want go back to fixed pointe i should do more test with the timing setup on the (SMCR 2011-01-03 14:35 wpwrak:  i replaced a constant with a for loop 2011-01-03 14:35 eek :) 2011-01-03 14:36 maybe try to get help from the people who have been working with SIE in the last months ? maybe they already know the problem or have solved it 2011-01-03 14:36 I need clen more stuff i wanted to confirm my theory of exotic timing tune in the Xburst EMC 2011-01-03 14:36 well.. there is an already solution 2011-01-03 14:36 but not compatible with ring buffer 2011-01-03 14:37 cause it requires start a reading, wait it finish, then read the collected data and start again.. 2011-01-03 14:37 kind of slow for what i'm looking (stream gps raw data as it arrives) 2011-01-03 14:38 Well i already wrote to qi list with cc to carlos, and dint get other replies besides the one you can see :-) 2011-01-03 14:38 Anyway i'm learning a lot with all this issues :-) 2011-01-03 14:38 s/issues/ignorance from my side 2011-01-03 14:39 maybe ask a bit more specifically, e.g., whether any of carlos's students has done something similar. then poke that guy. 2011-01-03 14:39 The ADC is the most similar 2011-01-03 14:39 and it works as i already pointed 2011-01-03 14:39 the fragile timing doesn't sound good. if you don't solve this early, you'll never be able to trust your results. 2011-01-03 14:40 They still need a IRQ glag implemented as a register 2011-01-03 14:40 yeah, i need trust my results indeed 2011-01-03 14:40 i alredy send one to be analized i'm hoping get results back soon 2011-01-03 14:40 i'd still kinda suspect caching. but the symptoms don't match exactly 2011-01-03 14:41 I'll do few more test i think i'm close 2011-01-03 14:41 e.g., i would expect the cache to almost never change, since you're probably in a very tight loop with a small working set 2011-01-03 14:41 but then, maybe you're not. in which case the cache could be pretty erratic. 2011-01-03 14:42 hmm 2011-01-03 14:46 kristianpaul: have you checked that the memory region into which the FPGA is mapped is uncached ? 2011-01-03 14:48 i think a quick indicator should be to see if the region is listed in /proc/iomem 2011-01-03 14:49 no 2011-01-03 14:49 to access the FPGA, do you mmap /dev/mem ? 2011-01-03 14:51 or do you have some dedicated device in /dev ? or maybe some library that handles the mapping for you ? 2011-01-03 14:51 yes (/dev/mem) 2011-01-03 14:54 wpwrak: how i can know if it is cached? 2011-01-03 14:54 hmm, a little suspicious. i wonder what cache settings the kernel defaults to when nothing specific is set 2011-01-03 14:55 maybe let's try something else first 2011-01-03 14:55 can you write to the FPGA, or only read ? 2011-01-03 14:56 write to 2011-01-03 14:56 s/to/too 2011-01-03 14:56 okay, then maybe try this: disable the writing. i.e., when you read you get X, then you write Y but the value is not stored. then the next read should yield X again. 2011-01-03 14:57 ok let me try 2011-01-03 14:57 (i hope :) all depends a bit on how the xburst handles such things, but it would be the "usual" way for uncached memory) 2011-01-03 14:58 larsc: what do you think ? 2011-01-03 14:58 what to i think about what? 2011-01-03 14:59 for finding out how whether caching is set, the only way i can think of is to walk the page tables. but that's messy. what your drivers normally do is just request the right kind of caching and you trust the kernel to do it right. 2011-01-03 14:59 is the fpga connected to the memory bus? 2011-01-03 15:00 larsc: it shares addr and data, so yes it is 2011-01-03 15:00 larsc: whether this test for caching would work on xburst: read read-only location X getting value Y, write Z != Y to X, then read X again. if you get Y, there's not cache. if you get Z, the CPU is caching the data. 2011-01-03 15:02 well if you mmap the uncached address it should work 2011-01-03 15:04 larsc: ah, uncached address ... that's an architecture detail i have to look up then :) 2011-01-03 15:04 KSEG1 is the keyword 2011-01-03 15:05 I dint get not Y either Z, so it should be okay 2011-01-03 15:05 kristianpaul: what is the address which mmap? 2011-01-03 15:06 neither Y nor Z ? that's scary ;-) 2011-01-03 15:06 0x15000000 2011-01-03 15:06 wpwrak: is not, well i dont changed the fpga, let me hardcode the reg ;-) 2011-01-03 15:08 kristianpaul: i think thats cached. 0xB5000000 is the uncached address 2011-01-03 15:08 larsc: should that be 0xb5000... ? 2011-01-03 15:08 hah ! :) 2011-01-03 15:08 hehe 2011-01-03 15:09 ah 2011-01-03 15:09 wait wait i'll set a read-only-reg on fpga first 2011-01-03 15:17 larsc: how do you know that is cached? 2011-01-03 15:17 and how wpwrak point the right address ? 2011-01-03 15:17 because it is in kseg0 and kseg0 is cached 2011-01-03 15:17 kseg1 is uncached 2011-01-03 15:17 XBurst-Core_Manual.pdf, page 35, figure 6-1 :) 2011-01-03 15:17 ah core.. 2011-01-03 15:18 i never looked that 2011-01-03 15:18 to get the uncached address from an cached address you have to OR it with 0xa0000000 2011-01-03 15:21 kristianpaul: and, did the result of your program change ? 2011-01-03 15:21 wait wait my cpu still is do syhtesis right now 2011-01-03 15:22 wpwrak: i get Y 2011-01-03 15:23 very good ! :) 2011-01-03 15:24 larsc: high five, i think ;-) 2011-01-03 15:24 but i was mapping 0x15000000 2011-01-03 15:24 kristianpaul: grrr. 2011-01-03 15:24 could be luck 2011-01-03 15:24 wait, i'll try 0xB5000000 2011-01-03 15:24 better use 0xb5... 2011-01-03 15:24 yeah, caches have a lot in common with schroedinger's cat 2011-01-03 15:25 i'm not used to systems with MMU. i see why i never tought in that... 2011-01-03 15:25 cache controllers with bug too. but they're nowhere near as bad as USB 2011-01-03 15:26 lekernel: having a fight with USB right now ? :) 2011-01-03 15:26 used too... getting it to work on MM1 was an horrible experience 2011-01-03 15:26 USB and SDRAM were the two worst things to fight with 2011-01-03 15:27 but at least SDRAM was interesting, I learned a lot 2011-01-03 15:27 hmm, this is fun. one of my disks is failing. (or maybe it's the mainboard - that pc had some issues before) meanwhile, the program is happily running, collecting data with nowhere to save it. this will be fun :) 2011-01-03 15:27 and there are still some USB bugs it seems...grr 2011-01-03 15:28 they only happen with certain devices, of course 2011-01-03 15:28 mine work correctly 2011-01-03 15:28 the joy of interoperability :) 2011-01-03 15:28 "certain devices" = certain MM1 or certain things they connect to ? 2011-01-03 15:28 certain things they connect to 2011-01-03 15:29 the MM1 USB hardware is simple enough not to have board-to-board variations (except poor solders joints, we had that too) 2011-01-03 15:29 that's the evil part, yes 2011-01-03 15:29 hmm are you sure about 0xb500? my Xbusrt is jz4725 2011-01-03 15:30 I said cause i'm not reading what is on sra-on-fpga.. 2011-01-03 15:30 kristianpaul: they should be all the same 2011-01-03 15:34 hmm :/ 2011-01-03 15:39 are there any readable SIE schematics ? 2011-01-03 15:40 (the ones in schhist are undecipherable) 2011-01-03 15:41 kristianpaul: it works with 0x1500... but not with 0xb5000..., thats strange. can you show the code? 2011-01-03 15:41 wpwrak: http://projects.qi-hardware.com/index.php/p/nn-usb-fpga/source/tree/master/KICAD_design_files/SAKC_PCB_v2 2011-01-03 15:41 larsc: yes wait a min 2011-01-03 15:42 larsc: http://paste.debian.net/103705/ 2011-01-03 15:43 map function comes from  this http://paste.debian.net/103706/ 2011-01-03 15:44 kristianpaul: you have to declare virt_addr as volatile int * 2011-01-03 15:45 well thats a sie example i tought was okay i jsut added the extra reading part and changed the memmory addr to map 2011-01-03 15:46 reads about volatile variables 2011-01-03 15:46 if it's not "volatile", the compiler is free to do whatever it pleases there. no, that's not okay :) 2011-01-03 15:47 oh 2011-01-03 15:47 the gpio address should also be 0xb1301... 2011-01-03 15:48 ah 2011-01-03 15:48 wait 2011-01-03 15:48 larsc: i actually wonder what happens with the SoC registers. i used 0x1... quite  alot and didn't notice any problems 2011-01-03 15:50 larsc:of course, maybe i was just a lot luckier than kristianpaul  :) 2011-01-03 15:58 hhm. tried the thing with the blinkenlight. with 0x1..., it works. with 0xb..., it doens't. interesting. 2011-01-03 16:00 hmm, thinking of it ... do kseg# really work like this ? i mean with mmap ? 2011-01-03 16:00 0xb on my side and now get messier :S 2011-01-03 16:00 hm, ok seems as if kseg1 is only accessible in kernel mode 2011-01-03 16:01 is it 0xb1301000 right? 2011-01-03 16:01 larsc: so no *b* after all? 2011-01-03 16:01 kristianpaul: wait a moment :) i think we need a plan B ... 2011-01-03 16:02 (but not 0xb ;-) 2011-01-03 16:03 probably the first solution was ok 2011-01-03 16:03 i guess O_SYNC does the trick 2011-01-03 16:08 larsc: so resuming, there is no cached thing at 0x01500000 ? 2011-01-03 16:11 actually i'm not sure 2011-01-03 16:11 [commit] David Kühling: octave: install Octave development libs&scripts to staging_dir http://qi-hw.com/p/openwrt-packages/244c849 2011-01-03 16:11 [commit] David Kühling: Port of plplot: a plotting library supporting most scripting languages http://qi-hw.com/p/openwrt-packages/0a1980c 2011-01-03 16:13 i find the O_SYNC a bit dubious, too 2011-01-03 16:13 kristianpaul: but ... let's go back to 0x1... but this time with volatile. does this improve things ? 2011-01-03 16:15 X getting value Y, write Z != Y to X, then read X again. i got Y 2011-01-03 16:16 but i have volatile on the code to get data from sige, i'll fix 2011-01-03 16:16 i dont have* 2011-01-03 16:26 larsc: ah yes O_SYNC could do the trick indeed. it implies O_DSYNC, which gets checked in drivers/char/mem.c:uncached_access 2011-01-03 16:27 learned something new :) 2011-01-03 16:33 kristianpaul: sorry about the misdirection with the cache. but let's see what the volatile does. 2011-01-03 16:35 [commit] Werner Almesberger: bbl.c (main): open /dev/mem with O_SYNC to disable caching http://qi-hw.com/p/ben-blinkenlights/76c0616 2011-01-03 16:35 [commit] Werner Almesberger: f32x: open /dev/mem with O_SYNC to disable caching http://qi-hw.com/p/f32xbase/6dbd844 2011-01-03 16:36 wpwrak: should i use that | O_SYNC on this code too  i guess? 2011-01-03 16:37 ah wait is already there :-) 2011-01-03 16:38 but you have it already via jz_mmap / jz_fpga_map, no ? or are you using something else ? 2011-01-03 16:38 yeha :) 2011-01-03 16:38 no no, 2011-01-03 16:54 [commit] Werner Almesberger: libbb/libbbd.c (main): open /dev/mem with O_SYNC to disable caching http://qi-hw.com/p/wernermisc/4a04cdc 2011-01-03 16:55 [commit] Werner Almesberger: atusb/cam: it's obsolete now - removed http://qi-hw.com/p/ben-wpan/2ac2420 2011-01-03 16:55 [commit] Werner Almesberger: atusb/cam2: renamed to atusb/cam http://qi-hw.com/p/ben-wpan/59ae88d 2011-01-03 16:55 [commit] Werner Almesberger: atusb/usb.sch: typo in VR1 footprint, should be 0402 instead of 0403 http://qi-hw.com/p/ben-wpan/04d3cec 2011-01-03 16:55 [commit] Werner Almesberger: atusb/usb.sch: typo: the LED is called LTST-C190KRKT, not LTST-C190KTKR http://qi-hw.com/p/ben-wpan/882558b 2011-01-03 16:55 [commit] Werner Almesberger: atusb/usb.sch: specified capacitance of TVSs (33 pF) and explained why http://qi-hw.com/p/ben-wpan/08eec5b 2011-01-03 16:55 [commit] Werner Almesberger: atusb/atrf.sch: changed C3, C8, C9 to "22pF/RF", to make BOOM select UHI Q type http://qi-hw.com/p/ben-wpan/9851e3c 2011-01-03 16:55 [commit] Werner Almesberger: tools/lib/atusd.c (atusd_open): open /dev/mem with O_SYNC to disable caching http://qi-hw.com/p/ben-wpan/f26d735 2011-01-03 17:18 @^&#$%&^$!^$& 2011-01-03 17:19 it looks like a bad configured serial port. 2011-01-03 17:19 Digi-Key Part Number AT86RF230-ZU-ND, Ship Date Estimate (mm/dd/yyyy) 4/13/2011 2011-01-03 17:20 someone just snatched up all the chips they had in stock :-( 2011-01-03 17:20 oh oh 2011-01-03 17:20 :-) 2011-01-03 17:20 hardware is fun 2011-01-03 17:27 indeed, i just fixed my wikireader too, seem the SD was fucked (dunno why happen this), so i will not recomend to buy "Team" branded micro SD/HC cards 2011-01-03 17:32 interestingly, the AT86RF231 is stocked all over the place 2011-01-03 17:32 the only problem with it is that, last time i checked, it was a non-export item 2011-01-03 17:33 wpwrak: where do you live btw? 2011-01-03 17:33 in buenos aires, argentina 2011-01-03 17:44 Any one can explain me for this: mmap (0, FPGA_SIZE, PROT_READ | PROT_WRITE, MAP_SHARED, fd, address); 2011-01-03 17:44 What is about PROT_READ and PROT_WRITE, ? 2011-01-03 17:45 this means that you can read and write to those registers 2011-01-03 17:46 ah ,pitty :-) 2011-01-03 17:46 tk 2011-01-03 17:48 hmm. i could order the at86rf231 without problem. maybe they lifted the ban. 2011-01-03 17:49 even better then. the 231 is slightly better. should be basically 100% compatible. 2011-01-03 17:50 yeah. the TI chip (CC2520) is still restricted, but the 231 is now orderable. phew :-) 2011-01-03 17:50 "FFT of a gps signals shows almost nothing except lots of noise, but if you have a very large gain before the antenna or a observatory antenna (like ESA or NASA) you can see the CDMA spectrum of GPS signal." 2011-01-03 17:51 oh well better i avoid it :-) 2011-01-03 17:52 So i'll jump to PRN matching just  (yay), but first lets fiinsh debuging the data acquisition :-) 2011-01-03 17:53 did switching to volatile help to make the fpga access more reliable ? 2011-01-03 17:55 ah yes i did voaltile 2011-01-03 17:56 I got almost same patter (data repeated twice) 2011-01-03 17:56 I'm just tracking/fixing a posible error i had defining some pointers ;-) 2011-01-03 18:02 nice. the 231 doesn't need an external input to enter test mode. this makes a few things easier. (one i/o can be removed from atusb and i don't have to hack one into atusd. wasn't looking forward to the latter at all.) 2011-01-03 18:02 (almost same pattern) :-( 2011-01-03 18:11 why are mircoprocessors banned from importing? 2011-01-03 18:12 transceivers. and they're banned from exporting, not importing 2011-01-03 18:12 apparently because they contain AES 2011-01-03 18:12 bad, bad excryption 2011-01-03 18:12 i see 2011-01-03 18:13 "if we let this fall into the wrong hands, the terrorists win" or the commies. or whatever ;-) 2011-01-03 18:13 well, seems that atmel got it cleared, while ti (with a similar chip) didn't 2011-01-03 18:15 heh, and they also added a - probably highly proprietary - high data rate mode in the new chip :) 2011-01-03 18:15 up to 2 Mbps. WLAN, here we come ! ;-) 2011-01-03 18:19 good. and they relaxed the frame retrieval timing. you still lose a frame if you're too slow, but it at least doesn't (partially) overwrite the old frame. 2011-01-03 18:24 and this means that i'll have to wait until the new chips arrive before making the new boards. good that i haven't started yet. but with some luck, i can keep the layout. (will be slightly sub-optimal for the one trace i could remove now, but that's a very minor issue) 2011-01-03 19:09 kewl. digi-key already processed my order. their speed is just crazy. 2011-01-03 19:26 hmm, NFC would interest me more 2011-01-03 19:27 and RFID in general 2011-01-03 19:31 too near :) 2011-01-03 21:18 hmm, the local-es list looks like another of these traps, where people can go thinking something is happening - but nothing is. interesting stats: http://lists.en.qi-hardware.com/pipermail/local-es/ 2011-01-03 21:36 tuxbrain around to get a quote... 2011-01-03 21:37 I bet some of then just swiched to english list 2011-01-03 21:39 yeah. the community is far from being big enough to need language-specific sub-communities. 2011-01-03 21:44 speaking of ghost towns, wolfgang: http://sharism.cc/ -> "News". maybe call them "Oldies" ? ;-) all the rest on that page is also kinda scary. one could think that everybody just caught the swine flu and died several months ago 2011-01-03 21:54 yes 2011-01-03 21:55 If you have troubles with this website please notify webmaster [at] sharism.cc . :p 2011-01-03 21:55 I guess is jsut usefull to pay by cc ;-) 2011-01-03 21:58 is getting cold here ~20 °C 2011-01-03 22:14 here too, only 25 C. i want my 30 C back ! 2011-01-03 22:14 haha 2011-01-03 22:15 26 C should and some fresh air should be fine :-) 2011-01-03 22:16 plenty of fresh air here, supposedly at 34 km/h (don't quite believe it) 2011-01-03 22:17 Are you watching the gnome applet for worlwide time/weather too ? :-) 2011-01-03 22:18 Amazing, so those guys relly desided not doing FFT on the FPGA and just then multyply and  do some serial seeking and  so on.. several times and with diffrent values in order to predict and for 11 channels ! 2011-01-03 22:19 wow 2011-01-03 22:19 http://www.gmat.unsw.edu.au/namuru/ 2011-01-03 22:19 is LGPL gut i'll dig on it later seriosully 2011-01-03 22:20 the more fun of all is that they have a comercial vesion too, wich is sold with all the features that a MM SoC have ! 2011-01-03 22:20 hehe 2011-01-03 22:20 wpwrak: i still getting two copies of data 2011-01-03 22:21 I'm starting to think that the refresh for the buffer is not so fast at all.. 2011-01-03 22:21 (gnome applet) no .. what's it called ? 2011-01-03 22:21 (copies of data) :-(( 2011-01-03 22:21 well is not an applet, sorry is just integrated with the default clock on latelly gnome versions 2011-01-03 22:22 I jsut dint knew how call it 2011-01-03 22:22 ah, so you need their desktop. naw, that i don't want :) 2011-01-03 22:22 what do you use then? 2011-01-03 22:23 grmbl. atmel had to introduce one change that makes the 230 pin-incompatible with the 231. couldn't resist, could they ? 2011-01-03 22:23 I like from gnome, the clock is always there, plus world time to track all of your  in differet place s is not bad 2011-01-03 22:23 (desktop) fvwm as window manager, no "desktop" 2011-01-03 22:23 ah 2011-01-03 22:24 for world time, i fire up kworldclock 2011-01-03 22:24 (atmel) oh yes they could :-) 2011-01-03 22:26 (kde) i cant talk about it i'm totally biased agains KDE :/ 2011-01-03 22:27 s/talk/use 2011-01-03 22:28 i use konqueror and kworldclock. not the rest. "desktops", no thanks :) 2011-01-03 22:31 (pin-incompatible) i'm curious if that change is actually for real ... 2011-01-03 22:34 now the fun part ... there are a few outputs they recommend connecting to ground if unused. now that's something that kicad's ERC really hates ... 2011-01-03 22:34 hmm 2011-01-03 22:35 more trouble then seems :/ 2011-01-03 22:35 ah, wind is picking up. we may still make those 34 km/h tonight 2011-01-03 22:35 oh, i hacked some ERC exception mechanism some time ago. the kicad folks didn't like it, but it's in our patch set. time to use it :) 2011-01-03 22:35 34 km/h is really fast, do you have something to make move with that wind? 2011-01-03 22:36 how could be a ERC exception? 2011-01-03 22:36 you mean like papers in my office ? ;-) 2011-01-03 22:36 i was thinking in wind energy 2011-01-03 22:37 (erc exceptions) like this: http://svn.openmoko.org/trunk/gta02-core/gta02-core.erx 2011-01-03 22:38 (wind energy) it also cleans my terrace :) 2011-01-03 22:38 i'm dont have that on my roof because there is no much too wind on a valley 2011-01-03 22:38 lol 2011-01-03 22:38 well thats fair :-) (clean) 2011-01-03 22:39 oh GPS P12/GPSMODE2 to GND 2011-01-03 22:39 Is my impresion or OM have a non deployed super alpha atempt to make a gps based navigation device? 2011-01-03 22:45 no no .. gta02-core was an attempt to build a more open gta02-like device, with left-over parts from openmomo 2011-01-03 22:45 alas, those parts never materialized :-( 2011-01-03 22:54 ah ok 2011-01-03 22:58 hmm i saw some pics of gta04 the other time 2011-01-03 23:01 did you ? 2011-01-03 23:06 http://lists.openmoko.org/pipermail/community/2010-November/063760.html 2011-01-03 23:08 ah, the beagle-crossover. not the "real" gta04 :) 2011-01-03 23:11 ah 2011-01-03 23:11 if i remember our numbering right, then gta04 was supposed to run in parallel with gta03, as an attempt to do more aggressive outsourcing. it was unceremoniously buried once the supposed outsourcers communicated their idea of an appropriate compensation :) 2011-01-03 23:12 DocScrutinizer probably would remember the details better than i do