**** BEGIN LOGGING AT Sun Apr 09 03:00:03 2017 Apr 09 03:04:30 Now...I can find out when that darn cat gets out. Apr 09 03:10:38 I came across an issue. What port should I use when using Flask on Debian with my BBB? Apr 09 06:02:00 gm Apr 09 06:53:57 zmatt: what is "vtp" when speaking about ddr? Apr 09 06:56:09 oh Apr 09 06:56:11 my Apr 09 06:56:52 hm, it sounds like I should not do VTP calibration while the DDR memory is still in self refresh. Apr 09 06:59:55 dgerlach: Looks like the "vtp_disable()" and "vtp_enable()" breaks my DDR when I resume. Apr 09 07:00:41 dgerlach: anything else in ds_save() and ds_restore() is harmless Apr 09 07:01:03 dgerlach: s/anything/everything/ Apr 09 07:10:59 oh you've got to be KIDDING me!! Apr 09 07:21:16 dgerlach: the vtp enable sequence is broken, the CLRZ toggle has a bug and corrupts the vtp_ctrl register Apr 09 07:21:22 dgerlach: since, ever. Apr 09 07:24:01 dgerlach: zmatt: https://ghostbin.com/paste/gr7yp line #19 Apr 09 07:32:35 afk Apr 09 11:05:11 Hello...I typed that a 2013 book was giving me trouble with Flask and the newer images/hardware. Apr 09 11:05:17 ...I figured out what went wrong. Apr 09 11:06:36 the BBB and variants of the BBB all need to have 192.168.7.2:5000 as the host and port. Apr 09 11:06:58 i.e. for Flask. Apr 09 12:48:58 noobs Apr 09 12:49:41 kind'a like ghosts. Apr 09 17:15:15 thinkfat: vtp is the output impedance calibration, it should normally be enabled whenever emif may be sending anything to the ddr, i.e. it should be disabled after ddr is in self-refresh and reenabled before taking it out of self-refresh Apr 09 17:16:05 (haven't looked at the link yet, I'm still waking up) Apr 09 17:21:07 zmatt: solved the problem already Apr 09 17:21:22 zmatt: simple, obvious bug in the vtp enable sequence Apr 09 17:22:01 zmatt: probably as old as the whole cortex-m3 firmware. I don't get how it was never found. **** ENDING LOGGING AT Mon Apr 10 03:00:00 2017