- boots from eNVM
- uses lim memory for RAM
- has console on uart 0
- has procfs enabled
- has most of nsh commands enabled

Signed-off-by: Jukka Laitinen <jukkax@ssrc.tii.ae>

- Change git repository urls to point to our tiiuae repos for nuttx & nuttx apps
- Remove most of the the build steps, leave just arm-12 and riscv;
	arm-12 has a build for stm32f7, and riscv for mpfs

Signed-off-by: Jukka Laitinen <jukkax@ssrc.tii.ae>

…ptimized version in tiiuae repo

Signed-off-by: Jukka Laitinen <jukkax@ssrc.tii.ae>

…iver to re-initialize on rx timeout

If the interface is UP, and no packets are received in 30s, re-initialize the interface by calling the
already implemented mpfs_txtimeout_expiry.

This is a temporary workaround for a bug where IF might be UP and working but packets can only
be transmitted. Receive side just doesn't work at all.

The original bug can be re-produced easily by disconnecting and reconnecting the ethernet cable while
the IF is up.

Signed-off-by: Jukka Laitinen <jukkax@ssrc.tii.ae>

SD-card clock speed is just forced to 50MHz. Note that to be correct, one should first set the SD-card
into high-speed mode, but currently NuttX doesn't support this.

With our cards, just setting the interface to 50MHz seems to work fine, and it removes the issue with
25MHZ clock causing disturbance on GPS bands. Typically cards which support high-speed mode just work with
50MHz interface clock.

This patch should be reverted when the NuttX supports high-speed mode, and we can properly set it.

Signed-off-by: Jukka Laitinen <jukkax@ssrc.tii.ae>

Signed-off-by: Jukka Laitinen <jukkax@ssrc.tii.ae>

…ootloader

This removes the need to have all the DDR/clock configuration related
"LIBERODEFS" flags defined, when not building a standalone/coldboot
configuration

All of this code is unused when not building with CONFIG_MPFS_BOOTLOADER

Signed-off-by: Jukka Laitinen <jukkax@ssrc.tii.ae>

This is not the correct way to do this, but it gives a nice perf. boost

Disable macOS builds for now.

All other commands are disabled in send_recv().

Signed-off-by: Jani Paalijarvi <jani.paalijarvi@unikie.com>

Signed-off-by: Jani Paalijarvi <jani.paalijarvi@unikie.com>

…ef and forward declare devif_loopback

Signed-off-by: Jukka Laitinen <jukkax@ssrc.tii.ae>

Signed-off-by: Jukka Laitinen <jukkax@ssrc.tii.ae>

… that takes care of the need for loopback

Remove unnecessary VQID shifting (16 -> 0).
Give an error if RPTUN init fails.

Enable LINUX_ON_HART4 in rpmsg-ch2 defconfig of ICICLE board.
Remove LINUX_ON_HART4 config from rpmsg-ch1 defconfig of ICICLE board.

Fix build warning when CONFIG_STM32F7_AUTONEG is not set

Signed-off-by: Jukka Laitinen <jukkax@ssrc.tii.ae>

…ved IO area in protected build

Signed-off-by: Jukka Laitinen <jukkax@ssrc.tii.ae>

Signed-off-by: Jukka Laitinen <jukkax@ssrc.tii.ae>

Signed-off-by: Jukka Laitinen <jukkax@ssrc.tii.ae>

Just a temporary patch, need to implement some kind of scalable solution
for this. It might be a good idea to map something else for the user
to avoid using ecall to enter the kernel for simple reads ?

Also, increase the L3 table size

There is no make step executed for this directory before the Kconfigure,
so all Kconfig's just need to be in-tree

Signed-off-by: Jukka Laitinen <jukkax@ssrc.tii.ae>

…ardenedOS

Workaround to avoid deadlock situation: The RX shall not try to wait for complete
frame in case there is RX errors detected.

In case mpfs_receive is called, it keeps waiting for complete frame and
also keeps the net_lock locked. In the mean while, the TX may run out of free
descriptors, but can not get net_lock mutex lock to be able to release used
descriptors. If there are no free TX descs it disables RX interrupts because
it may require to send response to the received frame.
So, TX side keeps RX interrupts disabled due to lack of free descriptors and
RX blocks TX to release those descs by stubbornly waiting for complete frame.

Signed-off-by: Jukka Laitinen <jukkax@ssrc.tii.ae>

…dress

Add a function to read PolarFire's serial number from system controller, and use the first five digits as device's mac address

Signed-off-by: Jukka Laitinen <jukkax@ssrc.tii.ae>

sendfifo() function need enable BWR_IE before checking if BWE is enabled
to avoid BWE to be activated between the BWE check and BWR interrupt
enabling, which causes the interrupt to be missed and Data Timeout error.

The user i/o area goes over 4MB, so need more page tables

If Linux kernel sends data, block all incoming msgs from the remote
end until an ack arrives, which completes the linux send data command.

If other than ack arrives, the logic in the Linux is no longer maintained,
causing the virtio marked broken.

Signed-off-by: Eero Nurkkala <eero.nurkkala@offcode.fi>

Utilize the sw flow control. Also detect situations where
both ack and msg present is set. In that case, consider
both flags.

Signed-off-by: Eero Nurkkala <eero.nurkkala@offcode.fi>

The thread conflicts with a HPWORK originated network operation,
taking the net_lock() recursive mutex, resulting in a deadlock.

Recursive mutexes are OK within the same task (HPWORK), so apply
the thread work into a work instead, which would potentially
resolve the very random conflict.

This increases the data throughput also a bit (10 - 20%).

Signed-off-by: Eero Nurkkala <eero.nurkkala@offcode.fi>

Add FPGA serial support, including console capabilities.
FPGA has UARTs from 0-7, so all UARTs starting from 5
depend on FPGA.

Signed-off-by: Eero Nurkkala <eero.nurkkala@offcode.fi>

Signed-off-by: Jukka Laitinen <jukkax@ssrc.tii.ae>

These are always the same as FPGA peripheral clock, so use that directly

Signed-off-by: Jukka Laitinen <jukkax@ssrc.tii.ae>

Don't turn off FIC3 clk which would terminate all other
peripherals depending on it.

Also add a few missing undefs.

Signed-off-by: Eero Nurkkala <eero.nurkkala@offcode.fi>

…mage

Signed-off-by: Jukka Laitinen <jukkax@ssrc.tii.ae>

…nuttx nxsem_tickwait_uninterruptible bug

The nxsem_tickwait_uninterruptible seems to timeout randomly one tick too soon. Add one tick to timeout to make sure it is long enough.

This can be reverted when the actual bug is fixed.

Signed-off-by: Jukka Laitinen <jukkax@ssrc.tii.ae>

…river change

Revert:
commit 1975878
Author: Huang Qi <huangqi3@xiaomi.com>
Date:   Mon Apr 11 18:42:24 2022 +0800

    arch/risc-v: Apply common mtime driver to mtime based chps

    Signed-off-by: Huang Qi <huangqi3@xiaomi.com>

As this breaks the systick

Signed-off-by: Jukka Laitinen <jukkax@ssrc.tii.ae>

…tloader

This is actually the same table as entrypoints, so just use the same data, which
can be set before booting any of the harts

Signed-off-by: Jukka Laitinen <jukkax@ssrc.tii.ae>

… bug in nuttx nxsem_tickwait_uninterruptible bug"

This reverts commit c9a794c.

…d by NuttX vs. opensbi

Signed-off-by: Jukka Laitinen <jukkax@ssrc.tii.ae>

- Fix retry counter handling and increase the maximum number of retries.
- Add some parenthesis for clarity.
- Change return type to signed int, as it may return -ETIMEDOUT
- Correct comment for returned value

Signed-off-by: Jukka Laitinen <jukkax@ssrc.tii.ae>

This cleans the unnecessary flow control that's no longer
needed.  Probably the support for simultaneous MP and ACK
changed the environment.

Also reorganize the mpfs_opensbi_*.S so that the trap
handler is easily relocated in the tlinker .ld file without
the need to relocate the utils.S.  This makes it easier to
follow the jump into other segment, eg. zerodevice.

Signed-off-by: Eero Nurkkala <eero.nurkkala@offcode.fi>

This loads the OpenSBI from eNVM into the zerodevice.

Signed-off-by: Eero Nurkkala <eero.nurkkala@offcode.fi>

Update to have 2k smaller version of OpenSBI.

Signed-off-by: Eero Nurkkala <eero.nurkkala@offcode.fi>

This reverts commit 95e02b0.

RPMSG is associated with the use of HPWORK / LPWORK queues.
After sending a message to the remote end (Linux), it waits
for an ack before proceeding.

Unfortunately this may take sometimes more than 0x3000 CLINT
MTIME cycles. Ack waiting is also unnecessary: nothing is done
with that information. Even worse, the net_lock() is also held
during the blocked time so it blocks other network stacks that
are unrelated to this.

The logic is still maintained with the message present (MP) flag.
No new message will be sent until that is cleared by the romote.

Signed-off-by: Eero Nurkkala <eero.nurkkala@offcode.fi>

SiFive document: "ECC Error Handling Guide" states:

"Any SRAM block or cache memory containing ECC functionality needs to be
initialized prior to use. ECC will correct defective bits based on memory
contents, so if memory is not first initialized to a known state, then ECC
will not operate as expected. It is recommended to use a DMA, if available,
to write the entire SRAM or cache to zeros prior to enabling ECC reporting.
If no DMA is present, use store instructions issued from the processor."

Clean the cache at this early stage so no ECC errors will be flooding later.

Signed-off-by: Eero Nurkkala <eero.nurkkala@offcode.fi>

…us check

It was checking a wrong register for dq/dqs window size.

Signed-off-by: Jukka Laitinen <jukkax@ssrc.tii.ae>

It doesn't make sense to try to auto-determine write latency, it may pass with too low value.

Keep the existing implementation if the write latency has been set to minimum
value, otherwise just set it.

Signed-off-by: Jukka Laitinen <jukkax@ssrc.tii.ae>

Especially the write calibration must bail out if the memory test timeouts,
otherwise the device will get stuck in running the memory test in sequence,
and it will always timeout.

Negative error value was also not properly returned from mpfs_mtc_test.

Signed-off-by: Jukka Laitinen <jukkax@ssrc.tii.ae>

… starting the training

Also move the DDRC clock enablement and reset to mpfs_init_ddr. This doesn't
change the functionality, but is the cleaner place for it.

Signed-off-by: Jukka Laitinen <jukkax@ssrc.tii.ae>

…g code

Implement the previously empty mpfs_ddr_rand with adapted "seiran128" code
from https://github.com/andanteyk/prng-seiran

This implements a non-secure prng, which is minimal in size. The DDR training
doesn't need cryptographically secure prng, and linking in the NuttX crypto
would increase the code size significantly for bootloaders.

Signed-off-by: Jukka Laitinen <jukkax@ssrc.tii.ae>

This reverts commit 8254b37.

This reverts commit 50a8ec6.

…reference code

Signed-off-by: Jukka Laitinen <jukkax@ssrc.tii.ae>
Co-authored-by: Eero Nurkkala <eero.nurkkala@offcode.fi>

Clean up the code and remove un-used global variables & structs

Signed-off-by: Jukka Laitinen <jukkax@ssrc.tii.ae>

Use a configuration register to set the upper address lines [37:32] for USB DMA engine.

Signed-off-by: Jani Paalijarvi <jani.paalijarvi@unikie.com>

Add the missing semicolons

Signed-off-by: Jukka Laitinen <jukkax@ssrc.tii.ae>

Signed-off-by: Jukka Laitinen <jukkax@ssrc.tii.ae>

This adds initialization of the ksz9477 switch when used instead of
a PHY, directly connected to SGMII

Signed-off-by: Jukka Laitinen <jukkax@ssrc.tii.ae>

… interrupts

- There are occasional extra STOPs being sent due to an IP bug when using an
  FPGA based I2C. Add a flag "inflight" to mask out extra STOP interrupts when
  using the FPGA based implementation
- There are no MPFS_I2C_ST_STOP_SENT irq's "initally". It is just already
  either success or still in progress

Signed-off-by: Jukka Laitinen <jukkax@ssrc.tii.ae>

Check that the base address and region size are properly aligned with
relation to each other.

With NAPOT encoding the area base and size are not arbitrary, as when
the size increases the amount of bits available for encoding the base
address decreases.

Calculate how long an I2C transation will take in microseconds, and use
this as the timeout for mpfs_i2c_sem_waitdone.

The reason for doing this is not to keep an i2c bus reserved for the full
1 second timeout, if e.g. a sensor is not on the bus / is faulty and
non-responsive. Reading the other sensors will be blocked for a relatively
long time (1 second) in this case. This fixes such behavior.

Fix a bug the destination buffer is not updated.
It is caused by the following commit.
commit 5d8d5bf

If the gulp size in the stdio buffer the remaining user buffer size it will:
- Corrupt memory in dest (user memory) and
- Keep corrupting KERNEL memory via the stdio character buffer until the
  whole system crashes, as the 'remaining' count underflows

This patch fixes this behavior.

…gv=NULL

The 'filename' parameter comes from user space and cannot be accessed
after calling ret = addrenv_select(binp->addrenv, &binp->oldenv); as
it changes the address environment and 'filename' points to who knows
where. In this case, calling nxtask_init(filename...) will cause a crash.

Solve this by making a local copy before changing address environment IF
argv = NULL. Why ? Because argv[0] contains the process name in this case
and the argument vector is already copied into kernel memory, thus
passing argv[0] to nxtask_init(argv[0]...) is safe.

The MPFS eMMC DMA has some requirements that are only fulfilled by
enabling separate DMA access buffers (FAT DMA buffers) and by forcing
indirect access to the media via FAT_FORCE_INDIRECT.

Why? Direct access to user buffers violates two things:
- Buffer alignment is not ensured
- Buffers are user memory (problematic in BUILD_KERNEL)

Signed-off-by: Petro Karashchenko <petro.karashchenko@gmail.com>

Signed-off-by: Xiang Xiao <xiaoxiang@xiaomi.com>

Signed-off-by: Xiang Xiao <xiaoxiang@xiaomi.com>

GCC13 have compatibility issue with libcxx (need libcxx 17+).

Please refer to: llvm/llvm-project#62396

Signed-off-by: Huang Qi <huangqi3@xiaomi.com>

Signed-off-by: Huang Qi <huangqi3@xiaomi.com>

Follow other risc-v based chips, and fix:
```
chip/rv32m1_irq.c: In function 'up_irqinitialize':
Error: chip/rv32m1_irq.c:98:3: error: array subscript -2048 is outside array bounds of 'uint8_t[2147483647]' {aka 'unsigned char[2147483647]'} [-Werror=array-bounds]
   98 |   riscv_stack_color(g_intstacktop - intstack_size, intstack_size);
      |   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /github/workspace/sources/nuttx/arch/risc-v/src/common/riscv_internal.h:40,
                 from chip/rv32m1_irq.c:36:
/github/workspace/sources/nuttx/arch/risc-v/src/common/riscv_common_memorymap.h:72:16: note: at offset -2048 into object 'g_intstacktop' of size [0, 2147483647]
   72 | EXTERN uint8_t g_intstacktop[];   /* Initial top of interrupt stack */
      |                ^~~~~~~~~~~~~
cc1: all warnings being treated as errors
```

Signed-off-by: Huang Qi <huangqi3@xiaomi.com>

Fix:
```
chip/esp_libc_stubs.c: In function '__retarget_lock_init':
Error: chip/esp_libc_stubs.c:246:14: error: passing argument 1 of '_lock_init' from incompatible pointer type [-Werror=incompatible-pointer-types]
  246 |   _lock_init(lock);
      |              ^~~~
      |              |
      |              struct __lock **
chip/esp_libc_stubs.c:181:26: note: expected 'int *' but argument is of type 'struct __lock **'
  181 | void _lock_init(_lock_t *lock)
      |                          ^
chip/esp_libc_stubs.c: In function '__retarget_lock_init_recursive':
Error: chip/esp_libc_stubs.c:251:24: error: passing argument 1 of '_lock_init_recursive' from incompatible pointer type [-Werror=incompatible-pointer-types]
  251 |   _lock_init_recursive(lock);
      |                        ^~~~
      |                        |
      |                        struct __lock **
chip/esp_libc_stubs.c:187:36: note: expected 'int *' but argument is of type 'struct __lock **'
  187 | void _lock_init_recursive(_lock_t *lock)
      |                                    ^
chip/esp_libc_stubs.c: In function '__retarget_lock_close':
Error: chip/esp_libc_stubs.c:256:15: error: passing argument 1 of '_lock_close' from incompatible pointer type [-Werror=incompatible-pointer-types]
  256 |   _lock_close(&lock);
      |               ^~~~~
      |               |
      |               struct __lock **
chip/esp_libc_stubs.c:193:27: note: expected 'int *' but argument is of type 'struct __lock **'
  193 | void _lock_close(_lock_t *lock)
```

Signed-off-by: Huang Qi <huangqi3@xiaomi.com>

Fix:
```
riscv-none-elf-ld: sotest.o: ABI is incompatible with that of the selected emulation:
  target emulation `elf64-littleriscv' does not match `elf32-littleriscv'
riscv-none-elf-ld: failed to merge target specific data of file sotest.o
```

Signed-off-by: Huang Qi <huangqi3@xiaomi.com>

Signed-off-by: Xiang Xiao <xiaoxiang@xiaomi.com>