**** BEGIN LOGGING AT Mon Jun 17 02:59:58 2019
Jun 17 05:04:31 <vaishnav98_[m]> jkridner ravikp7: I was able to create a new mmc_spi device for microSD click support, however I am getting an error: 'mmc1: unrecognised CSD structure version 2 ' when the card is inserted, I couldn't find much online resources to debug the issue
Jun 17 05:19:26 <jkridner[m]> Is SPI_DEBUG set? Can you look up what dev_dbg and pr_debug log and how to read it?
Jun 17 05:20:59 <jkridner[m]> Also, any chance the card isn’t good or the voltage is wrong?
Jun 17 05:45:03 <ds2> unrecogonized sounds like the CSD is not being xfered correctly
Jun 17 05:45:22 <ds2> can you do a hexdump of the CSD
Jun 17 05:45:57 <ds2> as far as I can tell, the voltage itself isn't a big deal as long as you can get SW to believe it is set to 3.3V
Jun 17 05:46:35 <ds2> (this is based on a misbuilt 1.8V board connecting to a SD card card that I had to ultimately hand wire in a level shifter)
Jun 17 07:14:24 * pratimugale[m] sent a long message:  < https://matrix.org/_matrix/media/v1/download/matrix.org/jCaDHFWzKbZHUAgnrvyeOLVR >
Jun 17 12:39:09 <vaishnav98_[m]> <jkridner[m] "Is SPI_DEBUG set? Can you look u"> jkridner: no , SPI_DEBUG is not set , will look the debug logs and update
Jun 17 12:41:21 <vaishnav98_[m]> <jkridner[m] "Also, any chance the card isn’t "> jkridner: The card and the click seems to be working well as there are no issues when loading the PB-microSD Click overlay , the voltage seems to be correct
Jun 17 12:42:22 <vaishnav98_[m]> <ds2 "can you do a hexdump of the CSD"> ds2: will do that and update :)
Jun 17 16:17:14 <pratimugale[m]> abhishek_ zeekhuge What should be the targets before the first evaluation and for this week?
Jun 17 16:27:41 <Abhishek_1> pratimugale : Will get back to you tomorrow
Jun 17 16:29:07 <Abhishek_1> pratimugale: Also saw your ideas list, first cut it looks good. Will have more feedback tomorrow.
Jun 17 16:29:58 <pratimugale[m]> abhishek_: Okay
Jun 17 20:14:53 <pratimugale[m]> zeekhuge abhishek_ Meanwhile I worked on restructuring the C - code to use the python daemon. It does compile but there are some issues with send, get msg. Will work on this and adding the memory functions to the daemon tomorrow (Tuesday)
Jun 17 20:16:10 <embden[m]> julieng: how can I find out in what mode processor is?
Jun 17 20:17:43 <embden[m]> without a debugger
Jun 17 21:46:29 <julieng[m]> <embden[m] "julieng: how can I find out in w"> embden you can find the mode in cpsr.
Jun 17 21:46:49 <julieng[m]> have a look at http://xenbits.xen.org/gitweb/?p=xen.git;a=blob;f=xen/arch/arm/arm32/head.S;h=5f817d473ea4cf38c8ad49f49032edfe83e4c877;hb=HEAD#l162
Jun 17 21:47:25 <julieng[m]> Why do you need to know the mode? I think it is sufficient to know we are not in hyp mode so likely something goes wrong.
Jun 17 21:48:58 <julieng[m]> <julieng[m] "have a look at http://xenbits.xe"> Xen provides an helper to print hexadecimal on the serial console (see putn) for early boot.
**** ENDING LOGGING AT Tue Jun 18 02:59:57 2019