<wpwrak>
about the hardest bit it correctly aligning the QFN chips. it's easy to overlook having them off by one pin. and of course, that wouldn't go so well.
<eintopf>
you need some components from (baumarkt) and drugstore, then you can build everything
<apelete>
[ 1.970000] couldn't find an available UDC
<apelete>
"missing bulk" message seems to come from ep_config_from_hw() which is called by musb_init_controller()
<apelete>
reading from musb_core.c code, couldn't see what's needed in order to get the usb endpoints config right
<apelete>
mth larsc: I added a j4740_musb_set_vbus() in glue layer but that didn't cut it, any idea ?
bzb has quit [Remote host closed the connection]
<DocScrutinizer05>
set vbus is a tricky thing, since it depends on the particular device and how it implemented VBUS-boost and charging. Make DAMN SURE you switch off the charging before you enable vbus boost, or you might fry the hardware
<DocScrutinizer05>
you also don't want to enable 5V VBUS boost before you disabled any gadget driver that would try to start ENUM when detecting 5V on VBUS. Likewise you don't want to enable gadget mode (B) in musb_hdrc (after exit from hostmode A and thus disabling the booster) before any voltage buffered in capacitors on VBUS got discharged and voltage level is <2some Volt. Otherwise, see above
<apelete>
DocScrutinizer05: thanks for the warning, wasn't aware of that :). how am I supposed to swith off the charging on the nanonote ?
<DocScrutinizer05>
sorry, no idea
<DocScrutinizer05>
no schematics at hand
<apelete>
maybe I shouldn't be using the usb port to power the device (like I'm doing right now), and rely on the batteru instead until vbus setting is ok
<apelete>
s/batteru/battery
<qi-bot>
apelete meant: "maybe I shouldn't be using the usb port to power the device (like I'm doing right now), and rely on the battery instead until vbus setting is ok"
<DocScrutinizer05>
booster and charger powering concurrently doesn't hurt either of both.
<DocScrutinizer05>
powering VBUS
<DocScrutinizer05>
what does harm is booster and battery charging circuitry enabled concurrently
<DocScrutinizer05>
battery charging circuitry is always enabled, or gets started/enabled as soon as 5V on VBUS get detected
<DocScrutinizer05>
it doesn't matter if a external power source is connected to USB
jekhor has joined #qi-hardware
<apelete>
good to know
wej has quit [Ping timeout: 264 seconds]
wej has joined #qi-hardware
kyak has quit [Ping timeout: 245 seconds]
jekhor has quit [Ping timeout: 272 seconds]
nse has quit [Ping timeout: 245 seconds]
kyak has joined #qi-hardware
kilae has joined #qi-hardware
<DocScrutinizer05>
you must avoid to "plug the UPS' mains plug into its own outlet"
<mth>
afaik the NanoNote doesn't support host mode; is VBUS ever driven by the device?
dos1 has joined #qi-hardware
<wpwrak>
there's no host mode nor is there anything to drive VBUS
<apelete>
mth: does that mean the set_vbus() call shoud return without doing anything ?
<mth>
I don't know if it can be empty or should disable vbus in some register
<apelete>
I used the jz4770 set_vbus() function as an example for jz4740
<mth>
does the old UDC driver contain any hints?
<mth>
the 4770 does support both device and host mode, so it's different from the 4740
<wpwrak>
openshot turned out to be surprisingly usable. limited, but at least the basic things aren't so hard to figure out.
kilae has quit [Quit: ChatZilla 0.9.90.1 [Firefox 24.0/20130910160258]]
<apelete>
mth: didn't see anything power related in old udc driver
<apelete>
in 4770, vbus setting seems to be handled with :
<apelete>
if (is_on) {
<apelete>
MUSB_HST_MODE(musb);
<apelete>
...
<apelete>
} else {
<apelete>
...
<apelete>
MUSB_HST_MODE(musb);
<apelete>
}
<apelete>
I guess jz4740 only need the "else" part, or am I overlooking something here ?
<apelete>
mth: oops, I meant:
<apelete>
if (is_on) {
<apelete>
MUSB_HST_MODE(musb);
<apelete>
...
<apelete>
} else {
<apelete>
...
<apelete>
MUSB_DEV_MODE(musb);
<apelete>
}
<apelete>
wpwrak: impressive progress with that anelok project of yours
<apelete>
been following on the mailing list, it baffles me how fast you're making this :-)
<wpwrak>
thanks ! :) it's actually not all that fast. alas, "real work" and the occasional social obligation get in the way ...
<apelete>
yeah well, since you're making both the hardware and software, it seems to be moving along pretty well if you ask me
dandon has joined #qi-hardware
<apelete>
looking at the video posted earlier make me want to buy one of these already. I hope you'll be able to get it manufactured :)
<wpwrak>
hehe, so do i :)
<mth>
I'm not sure you have to set the mode at all, if the pdata already states it is host-only
<mth>
but it would be worth checking the musb code that reads the pdata
<mth>
sorry, device-only
<apelete>
mth: ok, will check what's in the pdata. any idea about that "musb-hdrc: missing bulk" ?
<mth>
endpoints for bulk transfers?
<apelete>
I guess so, but can't figure out where the usb endpoints are supposed to be configured
<mth>
/* Max EPs scanned. Driver will decide which EP can be used automatically. */
<mth>
.num_eps= 6,
<mth>
(from struct musb_hdrc_config)
<mth>
so the musb core probably checks the hardware regs to figure out how many endpoints there are
<apelete>
so the number of ep found by usb core should match .num_eps in struct musb_hdrc_config ?
<viric>
grmbl there is no free codec for *interlaced* video. Neither theora or vp8 supports it.
<apelete>
mth: just tried ".num_eps = 4" in struct musb_hdrc_config since the old udc driver is advertising 4 endpoints
<apelete>
still getting "musb-hdrc: missing bulk" during boot though
<mth>
it says the number scanned, so the number found will be <= the number scanned
<mth>
adding logging to the scanning code would be useful
<mth>
to see if it is called, and if so, why it is rejecting endpoints
<mth>
is the hardware powered and its clock started before the scanning happens? (not sure if both are configurable, but most likely at least the clock is)
<apelete>
ok, will add logging to ep_config_from_hw() in musb_core.c to see what's happening exactly