| kristianpaul | Fallenou: MAXIMUM_FRAME_SIZE is not implemented on your driver, why? how do you handle the ethernet frames then? | 00:00 |
|---|---|---|
| Fallenou | in the driver I use MLEN as the max len | 00:16 |
| kristianpaul | in wich part fo the netwroking documentation is MLEN mentioned? | 00:18 |
| Fallenou | MLEN = MSIZE - sizeof(struct m_hdr) | 00:18 |
| kristianpaul | hmm may be mine is outdate.. Edition 4.10.99.0, for RTEMS 4.10.99.0 | 00:18 |
| Action: Fallenou is grepping through the source code, 1 min | 00:19 | |
| Fallenou | hum hum cannot find MSIZE | 00:24 |
| Fallenou | but I am pretty sure MLEN is something like 1500 | 00:24 |
| Fallenou | damn I cannot find any #define MSIZE anywhere | 00:28 |
| Fallenou | can you ? | 00:28 |
| Fallenou | maybe it's in the compiler header :o | 00:28 |
| Action: Fallenou is having a look | 00:29 | |
| Fallenou | ok yes it is | 00:29 |
| Fallenou | MSIZE = 128 | 00:29 |
| Fallenou | hum hum so it's the starting size of an mbuf | 00:29 |
| Fallenou | I guess it grows afterward | 00:30 |
| Action: Fallenou looking at his code | 00:30 | |
| Fallenou | hum hum strange I cannot find where I allocate memory inside the mbuf :o | 00:32 |
| Fallenou | could be our bug :) | 00:32 |
| Fallenou | maybe we just have the basic 128 bytes | 00:32 |
| Fallenou | and bigger frames will just overwrite memory | 00:32 |
| Fallenou | I will ask Joel about that :) | 00:33 |
| Fallenou | why the hell am I using MLEN in the packet structure instead of ETHERNET_FRAME_LENGTH | 00:35 |
| Fallenou | let fix that | 00:37 |
| CIA-40 | rtems-milkymist: Yann Sionneau master * r73572ad / c/src/lib/libbsp/lm32/shared/milkymist_networking/network.c : fixed length of data member of mm_packet struct to be ETHERNET_FRAME_LENGTH instead of MLEN - http://bit.ly/gTn785 | 00:38 |
| Fallenou | kristianpaul: I pushed a fix for the ethernet driver | 00:39 |
| Fallenou | I don't know if it will fix the FIFO problem | 00:39 |
| Fallenou | but it surely was a big issue | 00:39 |
| Fallenou | that would corrupt memory | 00:39 |
| Fallenou | kristianpaul: please compile the bsp and try again to make it crash :) | 00:40 |
| Fallenou | I emailed the rtems ML about that | 00:53 |
| Fallenou | thanks for the feed back kristianpaul :) | 00:53 |
| kristianpaul | Fallenou: he, i hope i works, i'll try it tomorrow or later midnight | 01:00 |
| kristianpaul | I need sump to work on the avnet, but thanks to jevin that will be quick i think :-) | 01:00 |
| kristianpaul | ergg i mean jackgassett: | 01:00 |
| Fallenou | ok great, keep me posted on your tests :) | 01:03 |
| Fallenou | I think this fix fixes something, but it may not be the problem you are talking about :) | 01:04 |
| Fallenou | we'll see ! | 01:04 |
| kristianpaul | what is something? | 01:05 |
| Fallenou | well I think it fixes a big memory corruption issue | 01:06 |
| Fallenou | inside the ethernet driver | 01:07 |
| Fallenou | when packets were > 128 bytes memory was overwritten somewhere | 01:07 |
| Fallenou | which isn't really cool :) | 01:07 |
| kristianpaul | heh | 01:09 |
| Fallenou | look at the patch, it's a one-liner-patch | 01:10 |
| adamw_ | larsc, last time I used: modprobe ftdi_sio vendor=0x20b7 product=0x0713 | 03:21 |
| adamw_ | to activate the JTAG/Serial pod | 03:21 |
| larsc | adamw_? | 03:23 |
| adamw_ | if I erased VID/PID info, then I use UrJtag tool & tried to 'cable milkymist', but I got 'Couldn't connect to suitable USB device. | 03:24 |
| adamw_ | Error: usbconn/libftdi.c:372 usbconn_ftdi_common_open() ftdi/ftd2xx error: ftdi_usb_open_desc() failed: device not found | 03:24 |
| adamw_ | ' | 03:24 |
| adamw_ | so this is reasonable. right? | 03:25 |
| kristianpaul | 20591:09:33 < lekernel> rmmod ftdi_sio | 03:25 |
| kristianpaul | 20592:09:34 < lekernel> modprobe ftdi_sio vendor=0x... product=0x... | 03:25 |
| kristianpaul | 20597:09:46 < wolfspraul> 1. "rmmod ftdi_sio" | 03:25 |
| kristianpaul | 20598:09:47 < wolfspraul> 2. "modprobe ftdi_sio vendor=0x20b7 product=0x0713" | 03:25 |
| kristianpaul | thats better | 03:25 |
| larsc | adamw_: if the vid/pid info is erased it makes sense that the driver does not handle the device | 03:26 |
| larsc | what does `lsusb` say? | 03:26 |
| adamw_ | yeah...Yanjun helped us to find the JTAG/Serial high speed bug on h/w | 03:26 |
| adamw_ | Bus 002 Device 038: ID 0403:6010 Future Technology Devices International, Ltd FT2232C Dual USB-UART/FIFO IC | 03:27 |
| adamw_ | this info( be noticed that I erased VID/PID already) | 03:27 |
| larsc | so you should be able to get it working with `rmmod ftdi_sio; odprobe ftdi_sio vendor=0x0403 product=0x6010` | 03:27 |
| kristianpaul | rmmod ftdi_sio; modprobe ftdi_sio vendor=0x0403 product=0x6010 | 03:28 |
| adamw_ | hmm...with 'dmesg', I can see two device attached to ttyUSB0 and ttyUSB1 | 03:29 |
| kristianpaul | hmm | 03:29 |
| adamw_ | so I found that strange things that if I used "modprobe ftdi_sio vendor=0x20b7 product=0x0713" & programmed ftdi to be correct '0x20b7' & '0x0713' | 03:30 |
| adamw_ | then I just got only ttyUSB0 only, ttyUSB1 disappeared...what could cause this? | 03:30 |
| kristianpaul | ttyUSB1 is actually jtag so should be okay | 03:31 |
| kristianpaul | does it said too "Ignoring serial port reserved for JTAG" ? | 03:32 |
| adamw_ | no.. | 03:32 |
| adamw_ | ttyUSB0 is jtag, ttyUSB1 is serial | 03:32 |
| adamw_ | kristianpaul, http://en.qi-hardware.com/wiki/File:M1_jtagserial_run1_C27_ground_rework3.png | 03:33 |
| adamw_ | this fixed the high speed bug | 03:33 |
| adamw_ | so after I fixed this, then I tried to follow all steps on http://en.qi-hardware.com/wiki/JTAG_Serial_Cable_run_1_for_Milkymist_One#Tests_and_Results | 03:35 |
| adamw_ | then I got only ttyUSB0 only. | 03:35 |
| adamw_ | so I erased VID/PID then 'dmesg'...i got two device attached! | 03:36 |
| larsc | should be fine. there is code in the driver which tells to don't create a ttyUSB for the jtag port, when VID/PID matches those of the milkymist jtag adapter | 03:36 |
| adamw_ | but i got failed while running 'jtag''s 'cable milkymist'. :-) hope you understand my descriptions. | 03:36 |
| kristianpaul | why you erased VID/PID? you mean in the eeprom? | 03:38 |
| larsc | adamw_: did it fail for the MM VID/PID or the default VID/PID or both? | 03:39 |
| adamw_ | i didn't see the replied msg of 'dmsg' about attaching two device, so after I erased VID/PID then my laptop can detect both. | 03:41 |
| kristianpaul | you dont need reply about attaching two devices | 03:41 |
| adamw_ | with MM VID/PID, I got ttyUSB0 only; with default VID/PDI, i got both. | 03:42 |
| larsc | adamw_: thats the correct result | 03:42 |
| adamw_ | so what action I need to do now? | 03:42 |
| kristianpaul | jtag | 03:42 |
| kristianpaul | cable milkymist | 03:43 |
| kristianpaul | detect | 03:43 |
| adamw_ | erase back to MM VID/PID...then jtag..cable milkymist ..detect ? | 03:43 |
| larsc | yes | 03:43 |
| kristianpaul | yes | 03:43 |
| larsc | that should work | 03:43 |
| adamw_ | good...second. | 03:43 |
| kristianpaul | nice bug fix btw :-) | 03:44 |
| roh | at openmoko we always had 2 serials as far i can remember... and one vanished as soon as openocd was started | 03:44 |
| larsc | urjtag checks the VID/PID and if it doesn't match you'll get the error you've seen | 03:44 |
| kristianpaul | larsc: did you finally try openocd with lm32? | 03:45 |
| kristianpaul | or was mwalle .. | 03:45 |
| larsc | kristianpaul: i couldn't getit to work | 03:46 |
| kristianpaul | adamw_: does it works? | 03:52 |
| adamw_ | good, jtag port/coonection surely work well. | 03:53 |
| adamw_ | but my ttyUSB1 can't work well since I need to use it to test serial port connected to M1. | 03:53 |
| kristianpaul | hmm? | 03:54 |
| adamw_ | flterm --port /dev/ttyUSB1 --kernel boot.bin | 03:54 |
| adamw_ | i used this to test 'serial' port | 03:55 |
| kristianpaul | why /dev/ttyUSB1 and not /dev/ttyUSB0 ?? | 03:55 |
| adamw_ | with 'dmesg', I still didn't the ttyUSB1 | 03:55 |
| kristianpaul | i still confused about your setup | 03:55 |
| kristianpaul | you should not get ttyUSB1 jut ttyUSB0 | 03:56 |
| kristianpaul | try | 03:56 |
| kristianpaul | flterm --port /dev/ttyUSB0 --kernel boot.bin | 03:56 |
| adamw_ | hm...oah...MAN! I totally made mistakes on last 97pcs productions...No one found. | 03:58 |
| adamw_ | yes, now just used ONLY ttyUSB0 to both 'jtag' & 'serial' ports. | 03:58 |
| adamw_ | god! my steps of productions were totally wrong! | 03:59 |
| kristianpaul | did detect command in urjtag work? | 03:59 |
| adamw_ | yes, it works well now.;-) | 04:00 |
| kristianpaul | You got ginally fpga id? | 04:00 |
| kristianpaul | great ! | 04:00 |
| kristianpaul | gn8 then ! | 04:00 |
| adamw_ | kristianpaul, larsc Much thanks for helps | 04:00 |
| adamw_ | I'll send rework steps to list for high speed bug | 04:01 |
| adamw_ | kristianpaul, I think you can directly rework on your side.;-) | 04:01 |
| adamw_ | the ground of C3/R14/C27/C28 doesn't connect with system ground. | 04:02 |
| kristianpaul | adamw_: yeah ! | 04:02 |
| kristianpaul | adamw_: i'll wait impatietly for the steps | 04:04 |
| adamw_ | you could just follow: | 04:06 |
| adamw_ | http://en.qi-hardware.com/wiki/File:ECO_Yanjun_jtagserial_run1.png | 04:06 |
| adamw_ | http://en.qi-hardware.com/wiki/File:M1_jtagserial_run1_C27_ground_rework1.png | 04:07 |
| adamw_ | http://en.qi-hardware.com/wiki/File:M1_jtagserial_run1_C27_ground_rework2.png | 04:07 |
| adamw_ | http://en.qi-hardware.com/wiki/File:M1_jtagserial_run1_C27_ground_rework3.png | 04:07 |
| adamw_ | well...starts to edit wiki now...We do apology. | 04:08 |
| kristianpaul | ah, just two points? | 04:08 |
| adamw_ | right! | 04:08 |
| kristianpaul | i'll do it NOW | 04:08 |
| adamw_ | you can handle i think ...but for s/w and whole documents I must edit more... | 04:09 |
| adamw_ | ok..good to have you guys supports. | 04:09 |
| adamw_ | one question again: why my last time of production steps can work with ttyUSB1 (for flterm...) and ttyUSB0( for Urjtag..)? | 04:12 |
| adamw_ | i confuse myself now..:-( | 04:13 |
| kristianpaul | no | 04:20 |
| adamw_ | kristianpaul, ? | 04:21 |
| kristianpaul | actually you dont need to tell urjtag about ttyUSB | 04:21 |
| adamw_ | no, i meant that my last time production i used 'flterm --port /dev/ttyUSB1 ...' then it can work? | 04:22 |
| kristianpaul | i wonder how/why it worked for you | 04:23 |
| kristianpaul | It should not.. as serial port is attached as /dev/ttyUSB0 | 04:23 |
| adamw_ | and now with fixed high speed problem...i can't use ttyUSB1 anymore...? | 04:23 |
| kristianpaul | right | 04:23 |
| kristianpaul | well | 04:23 |
| kristianpaul | at least, you plug another usb2ttl cable or somthing that already take /dev&ttyUSB first so the jtagserial port will be ttyUSB1 | 04:24 |
| adamw_ | so last time must have some things I still made mistake somewhere? o | 04:25 |
| adamw_ | you are right! | 04:26 |
| adamw_ | it indeed also shows 'Ignoring serial port reserved for JTAG' on ttyUSB0. | 04:27 |
| kristianpaul | yes | 04:28 |
| kristianpaul | http://paste.debian.net/107552/ | 04:28 |
| kristianpaul | !!! | 04:28 |
| adamw_ | great! yours now is high speed! | 04:29 |
| kristianpaul | yes, was easy rework | 04:29 |
| kristianpaul | and i'm bit sleepy now | 04:29 |
| adamw_ | what's command you typed? | 04:29 |
| adamw_ | ha...ok | 04:29 |
| adamw_ | sleep first | 04:30 |
| kristianpaul | well i just ram some already made scripts for jtag to both flash bitstream and the app | 04:31 |
| kristianpaul | it works as usual, now a bit faster it seems | 04:31 |
| kristianpaul | ok, bed time now | 04:31 |
| kristianpaul | chao ! | 04:31 |
| adamw_ | cu! | 04:32 |
| wpwrak | hmm, regarding that jtag fix, did anyone actually measure what the difference between full-speed and high-speed mm1 jtag is ? | 14:34 |
| lekernel | rejon: playing with Ron a bit? ;) | 17:22 |
| wpwrak | heh, ron isn't here. that's kinda convenient ;-) | 17:26 |
| rejon | hahahah | 17:31 |
| rejon | its good to expose what we need to be working on | 17:31 |
| rejon | :) | 17:31 |
| rejon | bbiab gotta eat | 17:31 |
| wpwrak | rejon: i wouldn't mind the _exposing_ part. but if you had a limp, would you truly appreciate it if everyone you meet would mention it in every other sentence ? | 17:34 |
| wpwrak | rejon: or, for that matter, if most people would drop that topic after a while, but there's one guy who keeps on with it. | 17:36 |
| Fallenou | Is the minimac ethernet driver working well on Linux ? | 20:40 |
| Fallenou | can someone give me the link of the repository ? | 20:40 |
| larsc | https://github.com/tmatsuya/linux-2.6 | 20:41 |
| Fallenou | thanks | 20:41 |
| Fallenou | lekernel: the linux driver is using it's own crc32 function too btw :) | 20:42 |
| larsc | it should use the generic one though | 20:45 |
| Fallenou | yes that's what i've been told :p | 20:45 |
| Fallenou | was just joking around | 20:46 |
| lekernel | Fallenou: linux drivers aren't necessarily a good example | 20:50 |
| lekernel | if I didn't go after the Linux driver, it's only because I don't depend on Linux | 20:50 |
| Fallenou | sure sure | 20:50 |
| Fallenou | anyway the linux driver is not doing anything in the RX top half irq handler | 20:51 |
| lekernel | last time I tested, the ethernet linux driver didn't work at all | 20:51 |
| Fallenou | is there any RX fifo problem with linux ? | 20:51 |
| Fallenou | oooh | 20:51 |
| Fallenou | ok =' | 20:51 |
| Fallenou | so my looking at the code is irrelevant | 20:51 |
| lekernel | lol: http://designcon.techinsightsevents.com/video_contest | 21:00 |
| Fallenou | lol :') | 21:07 |
| Fallenou | awesome | 21:07 |
| mwalle | good evening | 22:28 |
| Fallenou | hi mwalle | 22:29 |
| lekernel | hi! | 22:31 |
| --- Tue Feb 15 2011 | 00:00 | |
Generated by irclog2html.py 2.9.2 by Marius Gedminas - find it at mg.pov.lt!
