You can use
```scala
your scala code here
```
```scala
your scala code here
```
@pwang7 assert(False, L"miaou $False", FAILURE) is fine for me
I prepared a simple example to illustrate the compiler error of the L"" interpolate in assert:
https://github.com/pwang7/SpinalAssertDemo
after clone the repo, just run ./run.sh to compile and it shows the error:
./run.sh
+ export MILL_VERSION=0.10.3
+ [ ! -f mill ]
+ MILL=./mill --no-server
+ ./mill --no-server version
[1/1] version
0.10.3
+ mkdir -p ./rtl
+ ./mill --no-server _.runMain AssertDemo
[31/42] demo.compile
[info] compiling 1 Scala source to /home/pwang/Downloads/code/SpinalAssertDemo/out/demo/compile.dest/classes ...
[error] /home/pwang/Downloads/code/SpinalAssertDemo/demo/src/demo.scala:12:3: overloaded method assert with alternatives:
[error] (assertion: spinal.core.Bool,message: Seq[Any])(implicit loc: spinal.idslplugin.Location): spinal.core.internals.AssertStatement <and>
[error] (assertion: spinal.core.Bool,message: String)(implicit loc: spinal.idslplugin.Location): spinal.core.internals.AssertStatement <and>
[error] (assertion: spinal.core.Bool,severity: spinal.core.AssertNodeSeverity)(implicit loc: spinal.idslplugin.Location): spinal.core.internals.AssertStatement <and>
[error] (assertion: Boolean,message: => Any)(implicit loc: spinal.idslplugin.Location): Unit
[error] cannot be applied to (spinal.core.Bool, spinal.core.LiteralBuilder#LList)
[error] assert(False, L"${REPORT_TIME} time: ${io.input.payload}")
[error] ^
[error] one error found
1 targets failed
demo.compile Compilation failed
can you tell me why?Please~
@allexoll Thanks ^^
class TopLevel extends Component {
val io = new Bundle {
val sink_data = in UInt(1 bit)
val sink_data_valid = in Bool()
val source_pam4 = out UInt(2 bits)
// val source_pam4_valid = out Bool()
}
val sink_data_r = Reg(UInt(2 bits))
sink_data_r := (io.sink_data , io.sink_data)type mismatch;
[error] found : spinal.core.UInt
[error] required: (Any, Any)
[error] sink_data_r := (io.sink_data , io.sink_data)
[error] ^
Should be considered as a experimental API
@Dongwei939 Ahhhh, sink_data_r := io.sink_data @@ io.sink_data
@@ is to concatenate 2 things and preserve the type (UInt/SInt)
## is for concatenate things in raw mode (always return Bits)
@kervel wrong channel ^^ ?
Hello, a few days ago Scala started printing warnings with assignments in my test benches: reflective access of structural type member value
start should be enabledimport dut.io
io.start #= true
It does not always print this message. What do you think about it?
Seems like at testbench runtime if i understand well
that's a weird one
compile time ?
sbt compile too
I mean, it is even before a
run or a runMain
Workaround: in
build.sbt, add scalacOptions ++= Seq("-language:reflectiveCalls") but I am not sure about what it does. And about the meaning of the warning, too ^^'
When this warning occurs, another one is printed, before the others:
No idea about what it is, maybe there is a link between the two?
[warn] dropping dependency on node with no phase object: uncurryNo idea about what it is, maybe there is a link between the two?
Another workaround seems to be:
class AesInterface extends Bundle {
val start = in Bool ()
val text, key = in UInt(128 bits)
val ready = out Bool ()
val cipher = out UInt (128 bits)
}
class Aes extends Component {
/* version with warnings
val io = new Bundle {
val start = in Bool ()
val text, key = in UInt (128 bits)
val ready = out Bool ()
val cipher = out UInt (128 bits)
}
*/
val io = new AesInterface
(The idea of rewriting it this way comes from: https://stackoverflow.com/questions/39202927/how-not-to-require-the-import-of-scala-language-relectivecalls which states that "The reason why you are getting this warning is that you have structural type reference or new {...} call somewhere in your test method.")
Also, defining interfaces this way could be good to document them and then generate documentation using sbt doc.
It may seem strange, but it is kind of like defining entity then architecture ^^'
i think i see
in scala, there is something realy weird, which is getting even worst in scala 3, the issue is that having
val yyy = new MyClass{
val xxx = 42
}
println(yyy.xxx) //Scala actualy use runtime reflection to access xxx from yyy, if i'm not wrong.
2 replies
For all, what's about having a https://opencollective.com/ SpinalHDL collective ? In order to collect and manage donations ?
Does somebody has opinion about it ?
Does somebody has opinion about it ?
3 replies