#apertus IRC Channel Logs

John_K: that is an excellent idea, I'll see if I can hook up the ACBUS to the I2C in the next revision

I think I understand the first half of the imagemagick script - take 3 copies of the raw bayered image, shift each one by one pixel either horizontally/vertically

not sure what the last half does though; -clone 2,3 -average \) -delete 2,3 -swap 0,1 +swap

they get avaraged and the originals are deleted

and finally we recombine

Bertl: aah, I forgot 2 X green sensels

John_K: okay, I hooked up ACBUS0 to PMOD_SCL and ACBUS1 to PMOD_SDA

but I have to test if that doesn't interfere with the I2C bus when the FTDI is not powered first

you may need to hook PMOD_SDA up to two pins on the FTDI in order to do I/O

(I've also only ever seen people use ADBUS0-2 for I2C, although I don't think there is any reason not to use ACBUS)

and as far as I know, the FTDI is not able to remap those functions

this should also allow to change the direction of SDA for reading

probably yeah

https://kelley.ca/temp/apertus-ftdi-bad.jpg

also https://kelley.ca/temp/apertus-ftdi-mag.jpg

trying to figure that out from the datasheet

the ftdi should power up and enumerate with nothing connected to the power board but the USB cable right?

hrm well this is weird then

AFAIK, the FT232HL requires 12MHz

huh the BOM states 24mhz

line 26, Q1

http://vserver.13thfloor.at/Stuff/AXIOM/BETA/axiom_beta_power_board_v0.23.bom

I hope nothing else was departed too much from it

me too

so, you know how to swap that out?

another question since you're here, there appears to be a strange swapping of diff-pair polarities from the main board to dummy interface board https://kelley.ca/temp/apertus-diff-pair.jpg

the thing is, the LVDS pairs on the sensor interface are not strictly N/P they will soon be labeled (when we document the interface) _A and _B

on the SFE, if you look closely, all the "upper" LVDS pairs are swapped

yeah

so it doesn't look like I have any 12MHz xtals kicking around here

you can use those tiny can crystals as well (typically used as clock crystals) if you find one with 12MHz

good to know

just did a few test with the FTDI, and I think we have a problem with an unpowered chip if we connect it to I2C

even test points for I2C would be helpful

I soldered to the hirose connector and it was a bit of a pain

the bus is there with SDA and SCL on different sides

but I'm wondering what the FTDI will do when we feed it from the 3V3 rail via a diode for example?

http://stefan.konink.de/contrib/apertus/

cool, thanks!

tar? yeah

hmm, can you open the ext4 partition (on the SD) there?

not easily

okay, I'll do a full image then, will be larger but simpler

you have a 16GB SD card or a smaller one?

so 16gb is fine

tbz2 or tar.xz work fine for me as well

yes, you will get a bunch of scripts, one of them initializes the GPIO extenders, another turns the power on, still another provides you with power readings

yes, they will be part of the image

I'm documenting my bringup steps as I go as well, will contribute them to the wiki

we will put all the stuff into proper repositories soon, it makes sense once other folks start working on them as well

happy to help get stuff into github as well if that helps

ahh

sure thing

the main problem at the moment is that we have several specialized Betas with different scripts and setups

makes sense

can always start with separate branches

how many units have you planned?

any ETA on the SD Card image?

understood

off for a nap ... bbl

back now ...

it seems that without the power board I get a ton of notices about sdhc1

I'm accessing via serial console right now, not via ethernet

oh?

ah, what do I need to modify for that?

ok

off to bed now ... have a good one everyone!