| Fallenou | thank you for your help wpwrak & lekernel | 00:00 |
|---|---|---|
| Fallenou | gn8 ! | 00:00 |
| wpwrak | it was fun :-) sweet dreams ! | 00:00 |
| Fallenou | yep :' | 00:01 |
| Fallenou | thanks see you | 00:01 |
| wolfspraul | cladamw: hi good morning! :-) | 00:50 |
| wolfspraul | another new week, wow | 00:50 |
| cladamw | hi good morning ! | 00:51 |
| wolfspraul | what's the plan this week? | 00:54 |
| wolfspraul | schematics are finished now? onto layout? | 00:54 |
| wpwrak | we still have a few open issues from the review. and two more things need looking at, SDRAM and the scary big FPGA | 00:56 |
| wpwrak | is would actually be good if sebastien could check the FPGA. i don't know a tenth of the quirks and restrictions it may have on its I/Os | 00:57 |
| wpwrak | s/is/it/ | 00:57 |
| wolfspra1l | hmm, I see | 01:03 |
| cladamw | wpwrak, power supply sheet replies from Werner I'll look at it, then we check fpga late tonight, I would combine all replied sheets then send a final M1R4, is it okay ? | 01:04 |
| wpwrak | sounds good | 01:13 |
| wpwrak | pity that we had so little public response to the review. based on the number of quite insightful suggestions we got on previous hardware issues, i had hoped for a bit more interest | 01:14 |
| wpwrak | well, maybe people just find reviews boring :) | 01:14 |
| wolfspra1l | not enough people that feel this is 'their' platform | 01:19 |
| wpwrak | perhaps, yes. they're not used to co-ownership yet | 01:20 |
| wolfspra1l | I think review can be understood as satisfying and fun, but you need to feel how this connects to your own use in the future | 01:20 |
| cladamw | boring may just not meet one's won designs. :( One may reply when seeing similar sch sheet alike 'their' platform. | 01:20 |
| cladamw | s/won/own | 01:20 |
| wpwrak | yes, there's always that chance | 01:21 |
| kristianpaul | fpga review looks time demading plus *i think* it should have done just once, or at least defiend over a baseline to follow | 01:43 |
| kristianpaul | i dunno that last part in the milkymist one history.. | 01:43 |
| kristianpaul | as wpwrak said, there are tenth quirks and restrictions about asigments on all over the banks about I/O, clocks, buffers and wonder what else i miss right now.. | 01:45 |
| kristianpaul | kind stuff imho should do just once :-) | 01:47 |
| wpwrak | that's basically my plan: look at the things we've changed ... and hope for the best for the rest ;-) | 01:51 |
| kristianpaul | :) | 01:52 |
| kristianpaul | wpwrak: that rule will apply for bitstream as well? | 02:01 |
| wpwrak | mh ? we don't review the bitstream :) | 02:04 |
| kristianpaul | sure, just kidding | 02:16 |
| wpwrak | besides, it's software. it can ripen in transit ;-) | 02:21 |
| kristianpaul | thats the worst part indeed | 02:22 |
| wpwrak | the ripening ? | 02:23 |
| wpwrak | why ? it ensures it arrives fresh | 02:23 |
| kristianpaul | hmm? | 02:23 |
| wpwrak | would you rather have it full of dessicated bugs ? ;-) | 02:23 |
| kristianpaul | lol, you are very good with words :) | 02:25 |
| wpwrak | maybe i should consider a political career | 02:26 |
| kristianpaul | in argentina? lol | 02:26 |
| wpwrak | i think, with a little effort, i can be very corrupt | 02:26 |
| wpwrak | and i've read Machiavelli. what else do you need ? | 02:27 |
| kristianpaul | just you ;) | 02:28 |
| kristianpaul | ergh, i corrupted the standy bitstream.. and forgot we're still "using" it | 02:29 |
| kristianpaul | for recovery right? no way get rid of it :-) | 02:29 |
| wpwrak | you can skip it via jtag :) | 02:30 |
| kristianpaul | hmm truth, where is the scriping fu when you needed | 02:38 |
| kristianpaul | but solved, i just reflash from my otherm milkymist upstream folder | 02:38 |
| stekern | Fallenou: you could add a watchdog to the wishbone accesses and generate an error on timeout | 03:32 |
| stekern | instead of just having the cpu hanging | 03:32 |
| GitHub58 | [flickernoise] xiangfu pushed 1 new commit to master: http://git.io/Cpk7zA | 03:32 |
| GitHub58 | [flickernoise/master] Ctrl+H: shortcuts help: combine some help messages - Xiangfu | 03:32 |
| Action: xiangfu try to use wpwrak's usb command for write full parse HID report :-) | 03:32 | |
| wpwrak | it's a messy one, isn't it ? :) | 03:33 |
| Action: xiangfu have more mouse that didn't working. the X/Y goes to 1024 etc.. | 03:33 | |
| xiangfu | wpwrak, trying ... | 03:33 |
| xiangfu | wpwrak, which file I should load ? softusb-input.bin? | 03:36 |
| xiangfu | no needs reboot any more and netboot. that same a lot of time | 03:41 |
| xiangfu | wpwrak, great feature for me. thanks | 03:42 |
| wpwrak | ah. now i understand which "usb command" you meant :) | 03:44 |
| xiangfu | wpwrak, I am try to add another one "usb restore" :-) | 03:48 |
| wpwrak | "return to factory settings" ? :) | 03:53 |
| wpwrak | you could of course just keep the original image on the M1, in ssd | 03:54 |
| xiangfu | wpwrak, yes. that one option. | 04:02 |
| xiangfu | I have a mouse. the hid report that have 10 buttons. but in fact it is just normal mouse. | 04:03 |
| xiangfu | like: | 04:03 |
| xiangfu | Usage Page (Button), ; Button (09h) | 04:03 |
| xiangfu | Usage Minimum (01h), | 04:03 |
| xiangfu | Usage Maximum (10h), | 04:03 |
| xiangfu | Logical Minimum (0), | 04:03 |
| xiangfu | Logical Maximum (1), | 04:03 |
| xiangfu | Report Count (16), | 04:04 |
| wpwrak | you mean 16 buttons ? | 04:15 |
| wpwrak | well, maybe that little mouse has great ambitions for the future ;-) | 04:15 |
| xiangfu | :-) | 04:15 |
| wpwrak | in any case, you should skip two bytes for its buttons, no matter how many there really are | 04:15 |
| xiangfu | I will only take care mouse hid descriptor on mouse buttons and x/y | 04:16 |
| wpwrak | a wise decision :) | 04:16 |
| cladamw | wpwrak, just measured U12 for actual temperature. :-) Your concern is right, but I don't think we need to change. :) A 478 mW(i.e. 39 C ) would be there for 149 mA out for video-in codec. The next problem is to put M1 in ambient 70 C is common ? or even 45 C ? | 06:56 |
| cladamw | if over 39 C, U120 almost starts to keep on 150 mA as constant. | 06:58 |
| cladamw | s/U120/U12 | 06:58 |
| wpwrak | what is your room temperature ? | 07:00 |
| cladamw | (C145/C234) wpwrak do you think it's okay for you if we change to 1uF/10uF or both 10uF ? | 07:00 |
| cladamw | my room temperature is now 23 C. | 07:00 |
| wpwrak | i'm just answering your mail :) (C145 et al. yes, perfect) | 07:01 |
| wpwrak | so add 16 C for a hot day :) | 07:01 |
| cladamw | wpwrak, yeah..sure, if put M1 in a hot day. :-) | 07:02 |
| wpwrak | well, mine survived such days. though i usually don't have the camera running. maybe i should :) | 07:04 |
| cladamw | it's good you can confirm and have a try, then we know the answer will get closer. :-) Happy to solve such mistakes though. :-) | 07:06 |
| cladamw | also about R62's 0.1W/0.05W in TI's ds. phew~ | 07:06 |
| wpwrak | subtle, eh ? ;-) | 07:10 |
| wpwrak | but it seems that we can also keep the 1/16 W. but better safe than sorry | 07:10 |
| wpwrak | particularly since the price is the same :) | 07:11 |
| cladamw | yes, let's change for 0603 package. | 07:11 |
| cladamw | since we don't know which one is correct is in TI's ds, so 0603 package( 0.1W ) is no 'sorry' .:-) | 07:12 |
| lekernel | Fallenou: CSRs (the bus ones), ethernet memory, and USB memory are non cacheable | 09:23 |
| GitHub76 | [flickernoise] xiangfu pushed 1 new commit to master: http://git.io/Pq1E1g | 09:27 |
| GitHub76 | [flickernoise/master] shellext: add usb restore for restore to default firmware - Xiangfu | 09:27 |
| Fallenou | ok | 09:31 |
| Fallenou | it's fixed now, the weird too high address is not accessed any more | 09:32 |
| Fallenou | gcc was missing some piece of information in the inline assembly to generate correct code (register cloberring) | 09:32 |
| Fallenou | 04:37 < stekern> Fallenou: you could add a watchdog to the wishbone accesses and generate an error on timeout < that would be cleaner indeed but what will the cpu do if wishbone says "ERR" ? it will retry ? and fail again ? thus hanging the whole system again | 09:34 |
| cladamw | wolfspraul, rii 2.4G keyboard received. it contains its own usb cable. | 09:48 |
| cladamw | xiangfu, new image supports Rii mini keyboard ? | 09:52 |
| xiangfu | cladamw, not the release image. | 09:54 |
| xiangfu | cladamw, if you want test the Rii mini keyboard. reflash it with --qi option. | 09:54 |
| cladamw | okay | 09:55 |
| cladamw | xiangfu, thanks. :) | 10:00 |
| wolfspraul | cladamw: what do you mean with 'its own usb cable'? | 10:02 |
| wolfspraul | you should have received a version that works with a wireless dongle | 10:02 |
| wolfspraul | you plug the wireless dongle into the m1, and use the riitek keyboard and mouse remotely | 10:02 |
| wolfspraul | is that what you got? | 10:03 |
| cladamw | wolfspraul, Rii mini equipped with its own usb cable to recharge battery. | 10:05 |
| wolfspraul | ah yes, true | 10:05 |
| wolfspraul | but you have the wireless version, right? | 10:05 |
| cladamw | right | 10:06 |
| wolfspraul | good | 10:08 |
| cladamw | xiangfu, which version is for Rii ? I mean "--qi [VERSION] [--data]" | 10:11 |
| xiangfu | just reflash_m1.sh --qi | 10:12 |
| xiangfu | is ok. | 10:12 |
| cladamw | okay | 10:12 |
| cladamw | ha~ nice ! control remotely very well. :-) | 10:31 |
| wolfspraul | and mouse included too | 10:32 |
| wolfspraul | we should have shipped like this from day 1, oh well | 10:32 |
| wolfspraul | but we can only learn as fast as we can, and improve, and keep moving | 10:32 |
| cladamw | yes, well.. but this tested by my own applied usb power switch patch, need to reopen new packed m1 to test again. :-) | 10:33 |
| cladamw | xiangfu, if I've never reflashed by '--qi --data', then directly '--qi', there's failed during compiling patch, so i go for ''--qi --data' again and without failure. right ? | 10:59 |
| cladamw | xiangfu, i seems like that from me, but I'd like to know as usal shipment steps of reflash. :-) Now i have to do: | 11:01 |
| cladamw | 1) reflash_m1.sh --qi --data 2) reflash_m1.sh --bios-mac XX XX | 11:01 |
| cladamw | correct me if i am wrong. | 11:02 |
| xiangfu | cladamw, (failed during compiling patch) it's normal. because there are some update on patches. if | 11:04 |
| xiangfu | cladamw, --qi --data will overwirte all patches. update them to latest. | 11:04 |
| cladamw | okay, so each m1 from me, must those two steps above. :-) | 11:04 |
| wpwrak | some day, we should think about what to do about patch and FN compatibility | 12:01 |
| mwalle | lekernel: wpwrak: why is sync 0x80 ? and not 0xff or 0x00 ? | 18:59 |
| wpwrak | errr, context please ? | 19:00 |
| mwalle | oh *g* :) | 19:00 |
| mwalle | USB | 19:00 |
| mwalle | softusb | 19:01 |
| mwalle | but i think i already found it | 19:01 |
| wpwrak | yeah. it's just how the pattern is defined. blame intel ;) | 19:05 |
| mwalle | wpwrak: yeah spec says, max. change of bits, so with nrzi that would be 0x00, i guessed | 19:08 |
| wpwrak | does it say that ? i see i section 7.1.10 "he SYNC pattern used for low-/full-speed transmission is required to be 3 KJ pairs followed by 2 K's for a total of eight symbols." | 19:22 |
| wpwrak | so that's 7 changes (0) followed by one non-change (1) | 19:22 |
| lekernel | mwalle: that's to provide an oscillating pattern to make the clock synchronization easier on the receiver | 19:32 |
| lekernel | and the last bit (MSB) to 1 disables the last transition, marking the end of the sync | 19:34 |
| mwalle | wpwrak: yeah you're right, dunno where i had that info from | 19:34 |
| mwalle | lekernel: so that marking is just an extra indication which can be checked | 19:39 |
| mwalle | or is there any technical reason for this? | 19:40 |
| larsc | you need to know where the packet ends | 19:41 |
| wpwrak | it's basically the start bit | 19:41 |
| wpwrak | e.g., the receiver may not see the entire SYNC pattern | 19:42 |
| qi-bot | The firmware build was successful, see images here: http://fidelio.qi-hardware.com/~xiangfu/build-milkymist/milkymist-firmware-20120319-2040/ | 21:19 |
| qi-bot | The firmware (using branch) build was successful, checkout the VERSIONS for detail, see images here: http://fidelio.qi-hardware.com/~xiangfu/build-milkymist/milkymist-firmware-20120319-2219/ | 22:59 |
| --- Tue Mar 20 2012 | 00:00 | |
Generated by irclog2html.py 2.9.2 by Marius Gedminas - find it at mg.pov.lt!