My matrix creator/Pi will not stay shutdown. I issue this command:
sudo shutdown -h now
It performs the shutdown immediately, but then boots right back up versus staying down so I can shut it off safely.
Is this normal with the Matrix creator attached?
Could it have something to do with me pulling up some of the Matrix Creator Expansion Port Pins to 3.3V with a 10M resistor?
Thanks,
Sean
Anyone have any thoughts on this one?
I tried myself and got the same result. Will share here if I find why is happening.
Thanks,
Thanks for verifying.
I read in some old forums that if you pull certain pins high, it takes it out of its halt state. Maybe its the state I’m leaving my Matrix Creator GPIO in before I sudo shutdown -h now.
-Sean
Any discoveries yet on how to keep the Matrix from rebooting after shutdown?
This really does seem to be a problem. I actually needed to shut down my pi yesterday, but the matrix was seemingly making it just reboot as stated here. It ended up irrevocably corrupting my SD card (to the point that dd/parted/fdisk etc couldn’t even do anything with it to recover or even reformat).
Kind of wondering now if I can just pull it off the pi entirely while it’s running, but that is also something I would prefer to avoid…
What you experienced is definitely the fear for all.
I imagine this has something to do with the matrix taking a pin high that results in taking a GPIO on the Pi high that turns it back on.
If that is the case, there may be hope in that one could have a program to shutdown that first drives those pins low.
However, I hope the guys who made the thing can dig through their drawings to know for sure.
See ya’,
Sean
I googled it and found this https://raspberrypi.stackexchange.com/questions/57994/prevent-wake-from-halt. Then, tested it and it looks like that is the same problem we are having with the MATRIX Creator. The I2C SCL pin at GPIO03 is rebooting the Pi.
I am making some test to see how we can make that the MCU does not use the I2C bus after sudo shutdown -h now and try to integrate that so is transparent for the user but that is not finished.
For now an idea of how to fix this would be:
shutdown
sudo shutdown -h now
For halting the MCU you can create a copy of the openocd file located at :
cd /usr/share/matrixlabs/matrixio-devices
sudo cp ./cfg/sam3s_rpi_sysfs.cfg ./cfg/sam3s_halt.cfg
sudo nano ./cfg/sam3s_halt.cfg
In the file, after target just leave init and reset halt like this:
...
target create sam3n.cpu cortex_m -endian little -chain-position 3
init
reset halt
shutdown
cd /usr/share/matrixlabs/matrixio-devices
sudo openocd -f cfg/sam3s_halt.cfg
sudo shutdown -h now
Note:
Next time you just make sure to do Step 3 before shutting down.
This is working for me now. Let me know if works for you guys too.
Will update here when this is solved.
-Yoel
Awesome! I can work with this by calling a script that issues the commands from my code.
One thing, step 3:
sudo openocd -f cfg/sam3s_rpi_halt.cfg
should be
sudo openocd -f cfg/sam3s_halt.cfg
There is the text “rpi” that wasn’t there in the prior steps.
The only other aspect is that any everloop LEDs on at the time of shutdown stay on. So, this will need to be handled by code prior to shutting down.
For example, if you have Alexa as a service, you’ll want to kill the service:
sudo systemctl stop YOURSERVICENAME
I then follow with a script to turn all the LEDs off.
The one blinking blue LED stays on as well if its caught on when it shutsdown. I haven’t figured out how to turn that one off.
Thanks for tackling this!
Sean
Great!
Just updated. Thanks 
I guess you are referring to the D48 LED in the MATRIX Creator, close to the Atmel SAM3S microcontroller. This LED is controlled entirely by the microcontroller. This blink is normally used to know if the program in the microcontroller is running. To remove the blinking, you could modify the firmware and use it to flash the MCU. If you are interested please create a new topic and I will be glad to help.
Will this be fixed? Just purchased the creator and ran into this problem, luckily found this topic and with the manual steps I was able to turn the Pi off but seems that this could/should be fixed permanently?
Although, seeing as this topic is from 2018 and the file mentioned hasn’t been updated since 2016 (according to Github) my hopes are not very high.
I was using the temporary fix - but this appears now no longer to work. I get pages of errors when I try to run sudo openocd -f cfg/sam3s_halt.cfg: Here is first few lines:
Open On-Chip Debugger 0.10.0-dev-g6165f43c-dirty (2019-06-27-05:36)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
SysfsGPIO nums: tck = 17, tms = 4, tdi = 22, tdo = 27
SysfsGPIO num: trst = 18
trst_only separate trst_push_pull
adapter speed: 128 kHz
Warn : em357.bs: nonstandard IR value
Warn : Specify TAP ‘sam3n.cpu.cpu’ by name, not number 3
Info : SysfsGPIO JTAG/SWD bitbang driver
Info : JTAG only mode enabled (specify swclk and swdio gpio to add SWD mode)
Warn : gpio 17 is already exported
Warn : gpio 4 is already exported
Warn : gpio 22 is already exported
Warn : gpio 27 is already exported
Warn : gpio 18 is already exported
Info : This adapter doesn’t support configurable speed
Info : JTAG tap: em358.cpu tap/device found: 0xffffffff (mfg: 0x7ff (), part: 0xffff, ver: 0xf)
Warn : JTAG tap: em358.cpu UNEXPECTED: 0xffffffff (mfg: 0x7ff (), part: 0xffff, ver: 0xf)
Error: JTAG tap: em358.cpu expected 1 of 1: 0x3ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x3)
Info : JTAG tap: em357.bs tap/device found: 0x004dffff (mfg: 0x7ff (), part: 0x04df, ver: 0x0)
Warn : JTAG tap: em357.bs UNEXPECTED: 0x004dffff (mfg: 0x7ff (), part: 0x04df, ver: 0x0)
Error: JTAG tap: em357.bs expected 1 of 1: 0x069aa62b (mfg: 0x315 (Ember Corporation), part: 0x69aa, ver: 0x0)
Info : TAP xc6sxl4.fpga.fpga does not have IDCODE
Info : JTAG tap: sam3n.cpu.cpu tap/device found: 0xfff159dd (mfg: 0x4ee (), part: 0xff15, ver: 0xf)
Warn : JTAG tap: sam3n.cpu.cpu UNEXPECTED: 0xfff159dd (mfg: 0x4ee (), part: 0xff15, ver: 0xf)
Error: JTAG tap: sam3n.cpu.cpu expected 1 of 1: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4)
Info : JTAG tap: auto0.tap tap/device found: 0x21f139ff (mfg: 0x4ff (), part: 0x1f13, ver: 0x2)
Info : TAP auto1.tap does not have IDCODE
Info : TAP auto2.tap does not have IDCODE
Info : TAP auto3.tap does not have IDCODE
Info : TAP auto4.tap does not have IDCODE
Info : TAP auto5.tap does not have IDCODE
Info : TAP auto6.tap does not have IDCODE
Info : TAP auto7.tap does not have IDCODE
Info : TAP auto8.tap does not have IDCODE
Info : TAP auto9.tap does not have IDCODE
Info : TAP auto10.tap does not have IDCODE
Info : TAP auto11.tap does not have IDCODE
Info : TAP auto12.tap does not have IDCODE
Info : TAP auto13.tap does not have IDCODE
Info : TAP auto14.tap does not have IDCODE
Info : TAP auto15.tap does not have IDCODE
Info : TAP auto16.tap does not have IDCODE
Warn : Unexpected idcode after end of chain: 145 0xe7ff0000
Warn : Unexpected idcode after end of chain: 177 0xfffffb8c
Warn : Unexpected idcode after end of chain: 209 0x043fffff
Warn : Unexpected idcode after end of chain: 241 0xffff8001
Warn : Unexpected idcode after end of chain: 273 0xfbffffff
Warn : Unexpected idcode after end of chain: 337 0xfff8043f
Warn : Unexpected idcode after end of chain: 401 0xfffe0010
Warn : Unexpected idcode after end of chain: 433 0xefffffff
Warn : Unexpected idcode after end of chain: 497 0x000087ff
Warn : Unexpected idcode after end of chain: 529 0x287c0000
Warn : Unexpected idcode after end of chain: 561 0x9e000000
Warn : Unexpected idcode after end of chain: 593 0x0000010f
Warn : Unexpected idcode after end of chain: 625 0x0030f800
Error: double-check your JTAG setup (interface, speed, …)
Error: Trying to use configured scan chain anyway…
Error: em358.cpu: IR capture error; saw 0x0f not 0x01
Warn : Bypassing JTAG setup events due to errors
Error: Invalid ACK (7) in DAP response
Error: Debug regions are unpowered, an unexpected reset might have happened
Error: Invalid ACK (7) in DAP response
Error: Invalid ACK (7) in DAP response
Error: Invalid ACK (0) in DAP response