Or better to say, can shutdown raise shutdown pin so board powers off really
Wherever you suggest is the proper place. From bitstream, this pin needs a kind of "fuze" logic in order not to be triggered at early start of bitstream when the LUTs set up and can do some glitch.. I use some counter that starts from 0 and must be clocked few times. shutdown pin is connected to MSB bit of this counter.
and already try the reboot ^^
@Dolu1990 yes reboot would be first step to make. For board shutdown it needs battery, configured RTC with alarm that triggers in the future and power from US2 or from US1 with green power LED set to OFF. I can assist with this
Or i should use the PROGRAMN FPGA input pin via USER_PROGRAMN from the schematic
For your this blackbox will be better if it works as it will reload current bitstream having saxonsoc in FPGA SRAM (regardless what in FLASH is)
@pnru_gitlab I have used your hwclock to calculate date but it does it with few days off :) https://github.com/emard/hwclock4saxonsoc can you check whats up wrong
Again very little time today. I indeed had an issue with being 1 day off when I did that I2C code - maybe my code in
date is also off and I now have matched errors on the Cortex :^). Here is a reviewed routine. @lawrie - in this form it is not suitable for c.lib, because it does not take an argument but works on a global var.
its called sakamoto-gregorian something
I think I took the algorithm in 4.2BSD as a base (several years ago). If I look at the code at the end of function gtime(), I think my reviewed routine is essentially the same (i.e. should be good).
The rewritten version is here now it matches with date -u --date="@<unix_seconds>" https://github.com/emard/hwclock4saxonsoc/blob/master/hwclock.c#L163 I dont know why it works :)
hwclock -s will set correct system date from RTC
So, i got the shutdown command in linux to successfully restart the FPGA
It's because althugh commanded to shutdown, RTC and green LED will keep waking up the board and shutdown pin will be ignored
I was asking myself why shutdown wasn't ok ^^
@Dolu1990 https://github.com/emard/ulx3s/blob/master/doc/MANUAL.md#low-power-mode is somehow tried to explain all prerequisites for real shutdown to happen. When conditions are met for real shutdown LED D11 on bottom side of board will be dimly lit. Only then shutdown pin=1 will be accepterd as real power off, otherwise ignored
else, i also tried with openocd via the telnet
but in short, unless you configure the RTC, you can't realy observe the feature
@emard I have updated the 12F 1core bitstream and opensbi (fw_jump.bin@0x340000) in Smp. You will need to flash the new fw_jump.bin@0x340000.
only shutdown can be used
@pnru_gitlab Do you know why lcc/bin/libs contains both softfloat and libsoftfloat and why it contains eeprintf? We do not include softfloat and eeprintf in c.lib.
Not sure. I think all the "extras" are test files once used during development and not needed in c.lib (because the final, debugged versions are included already).
I've asked Michael about the origins of his lib and it comes from a student / university project that looked at an optimized MIPS processor. All in all, as you already concluded there does not seem to be much point in keeping in line with "upstream".
@pnru_gitlab I added a version of your mktime - https://github.com/lawrie/riscv32_lcc/blob/master/lcc/bin/libs/time/mktime.c
ecppack --input ulx3s.config --svf ulx3s.svf
Failed to process input config: unrecognised config entry .sysconfig